Security Resilience

CVE-2024-10976

Postgresql 12.0 – 12.21

Published
14 November 2024
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 4.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0077 57th percentile
Risk Priority 37 floored blend · peak EPSS

CVSS 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

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

T1564.007 VBA Stomping Stealth
Adversaries may hide malicious Visual Basic for Applications (VBA) payloads embedded within MS Office documents by replacing the VBA source code with benign data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-10977Same product: Postgresql Postgresql
CVE-2026-14680Same product: Postgresql Postgresql
CVE-2026-14677Same product: Postgresql Postgresql
CVE-2026-14662Same product: Postgresql Postgresql
CVE-2026-6477Same product: Postgresql Postgresql
CVE-2026-14669Same product: Postgresql Postgresql
CVE-2026-19385Same product: Postgresql Postgresql
CVE-2024-7348Same product: Postgresql Postgresql
CVE-2024-4317Same product: Postgresql Postgresql
CVE-2026-2007Same product: Postgresql Postgresql

Affected Assets

postgresql
postgresql
12.0 — 12.21 · 13.0 — 13.17 · 14.0 — 14.14

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.3.4
  • V4.2.1
  • V7.1.3
  • V7.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.

PR.PS-06 mostly match
blocks

SSDLC practices directly address design-level state-consistency flaws during development.

DE.CM-09 partial match
blocks

Runtime data monitoring can surface consistency violations after they occur.

PR.DS-01 partial match
blocks

Integrity protections such as hashes or signatures can detect or prevent inconsistent state copies.

PR.IR-03 partial match
blocks

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.

prevents

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.

prevents

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.

References