Vulnerabilities > CVE-2024-10976 - Unspecified vulnerability in Postgresql

CVSS 5.4 - MEDIUM

Attack vector

NETWORK

Attack complexity

LOW

Privileges required

LOW

Confidentiality impact

LOW

Integrity impact

LOW

Availability impact

NONE

network

low complexity

postgresql

NVD

Published: 2024-11-14

Updated: 2025-02-11

Summary

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.

Vulnerable Configurations

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

References

https://www.postgresql.org/support/security/CVE-2024-10976/