CVE-2024-10976
Postgresql 12.0 – 12.21
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-10976 is a medium-severity Improper Preservation of Consistency Between Independent Representations of Shared State (CWE-1250) vulnerability in Postgresql. Its CVSS base score is 4.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique VBA Stomping (T1564.007); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-33374
Vulnerability Data
Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes. They missed cases where a…
more
subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy. This has the same consequences as the two earlier CVEs. That is to say, it leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.3.4V4.2.1V7.1.3V7.6.1
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
SSDLC practices directly address design-level state-consistency flaws during development.
Runtime data monitoring can surface consistency violations after they occur.
Integrity protections such as hashes or signatures can detect or prevent inconsistent state copies.
Resilience mechanisms often include state synchronization or replication protocols that enforce consistency.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.28 includes secure design and architecture with threat modelling, and its secure-coding practices touch on synchronization and race-condition awareness, so a well-implemented programme prevents some instances of distributed-state inconsistency; but CWE-1250 is fundamentally an architectural concern about coherence across independent components (the MMU-shadow example is hardware-level), which sits outside the slice of practice secure-coding training and peer review typically reach, leaving a nameable remainder.
A.8.30's contractual requirements for secure design (8.25), threat modelling (item c), and acceptance testing (8.29) can reach distributed-state-consistency defects when the supplier's design review and threat model explicitly address shared-state replication, but this is a specialised architectural concern that standard secure-development practices do not routinely cover, so only a minority of instances are prevented.