CVE-2024-10978 Affecting postgresql:15/postgresql-server-devel 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-8492467
  • published10 Dec 2024
  • disclosed4 Dec 2024

Introduced: 4 Dec 2024

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

How to fix?

Upgrade AlmaLinux:8 postgresql:15/postgresql-server-devel 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-server-devel package and not the postgresql:15/postgresql-server-devel package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

CVSS Scores

version 3.1