PostgreSQL up to 17.0 improper preservation of consistency between independent representations of shared state

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8	$0-$5k	0.00

Summaryinfo

A vulnerability was found in PostgreSQL up to 17.0. It has been rated as problematic. This impacts an unknown function. This manipulation causes improper preservation of consistency between independent representations of shared state. This vulnerability is tracked as CVE-2024-10976. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in PostgreSQL up to 17.0 and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a improper preservation of consistency between independent representations of shared state vulnerability. The CWE definition for the vulnerability is CWE-1250. The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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 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.

The advisory is shared at postgresql.org. This vulnerability is known as CVE-2024-10976 since 11/07/2024. The exploitation appears to be difficult. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 211488 (Debian dla-3954 : libecpg-compat3 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 12.21, 13.17, 14.14, 15.9, 16.5 or 17.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (211488) and CERT Bund (WID-SEC-2024-3475). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Gentoo Linux
• IBM Business Automation Workflow
• SUSE openSUSE
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Open Source PostgreSQL
• IBM Storage Scale
• IBM Sterling Connect:Direct
• IBM QRadar SIEM
• Progress Software WS_FTP
• Hitachi Ops Center
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain

Productinfo

Type

• Database Software

Name

• PostgreSQL

Version

• 12.0
• 12.1
• 12.2
• 12.3
• 12.4
• 12.5
• 12.6
• 12.7
• 12.8
• 12.9
• 12.10
• 12.11
• 12.12
• 12.13
• 12.14
• 12.15
• 12.16
• 12.17
• 12.18
• 12.19
• 12.20
• 13.0
• 13.1
• 13.2
• 13.3
• 13.4
• 13.5
• 13.6
• 13.7
• 13.8
• 13.9
• 13.10
• 13.11
• 13.12
• 13.13
• 13.14
• 13.15
• 13.16
• 14.0
• 14.1
• 14.2
• 14.3
• 14.4
• 14.5
• 14.6
• 14.7
• 14.8
• 14.9
• 14.10
• 14.11
• 14.12
• 14.13
• 15.0
• 15.1
• 15.2
• 15.3
• 15.4
• 15.5
• 15.6
• 15.7
• 15.8
• 16.0
• 16.1
• 16.2
• 16.3
• 16.4
• 17.0

License

• open-source

Website

• Product: https://www.postgresql.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.4
NVD Vector: 🔍

CNA Base Score: 4.2
CNA Vector (PostgreSQL): 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper preservation of consistency between independent representations of shared state
CWE: CWE-1250
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Nessus ID: 211488
Nessus Name: Debian dla-3954 : libecpg-compat3 - security update

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: PostgreSQL 12.21/13.17/14.14/15.9/16.5/17.1

Timelineinfo

11/07/2024 🔍
11/14/2024 +7 days 🔍
11/14/2024 +0 days 🔍
11/07/2025 +358 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: postgresql.org
Status: Confirmed

CVE: CVE-2024-10976 (🔍)
GCVE (CVE): GCVE-0-2024-10976
GCVE (VulDB): GCVE-100-284557
CERT Bund: WID-SEC-2024-3475 - PostgreSQL: Mehrere Schwachstellen

Entryinfo

Created: 11/14/2024 14:27
Updated: 11/07/2025 14:12
Changes: 11/14/2024 14:27 (62), 11/17/2024 01:36 (2), 05/10/2025 05:16 (12), 08/25/2025 06:13 (7), 11/07/2025 14:12 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

Do you know our Splunk app?

Download it now for free!