CVE-2024-10976 Affecting postgresql:15/postgresql-private-libs package, versions <0:15.10-1.module_el8.10.0+3929+38258aa5


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX8-POSTGRESQL-8492421
  • published10 Dec 2024
  • disclosed4 Dec 2024

Introduced: 4 Dec 2024

NewCVE-2024-10976  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 postgresql:15/postgresql-private-libs to version 0:15.10-1.module_el8.10.0+3929+38258aa5 or higher.
This issue was patched in ALSA-2024:10830.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql:15/postgresql-private-libs package and not the postgresql:15/postgresql-private-libs package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1