CVE-2024-10978

PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID

MEDIUM
4.2
CVSS Score
Published: November 14, 2024 at 01:00 PM UTC
Updated: June 17, 2026 at 06:56 AM UTC
2 products affected across 2 vendorsDebian LinuxPostgreSQL

Using PostgreSQL by N/A?

Get instant alerts when new vulnerabilities affect PostgreSQL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.2
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 12.2112.0 ≤ v < 12.2113 ≤ v < 13.1713.0 ≤ v < 13.1714 ≤ v < 14.1414.0 ≤ v < 14.1415 ≤ v < 15.915.0 ≤ v < 15.916 ≤ v < 16.516.0 ≤ v < 16.517 ≤ v < 17.1131415161717.017.0 beta117.0 beta217.0 beta317.0 rc1
Affected range stops below 12.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

Vendor Advisory
Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
https://www.postgresql.org/support/security/CVE-2024-10978/
Mailing List
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2024/11/msg00018.html
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2024/11/msg00011.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.2MEDIUMPostgreSQL
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-266NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card