CVE-2024-10978: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID

Published Nov 14, 2024
·
Updated

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 currentsetting('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.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

14 affected componentsFixes available
debian/postgresql-13<=13.16-0+deb11u1
13.20-0+deb11u1
debian/postgresql-15
15.12-0+deb12u215.10-0+deb12u1
debian/postgresql-17
17.4-1
PostgreSQL postgresql>=12.0<12.21
PostgreSQL postgresql>=13.0<13.17
PostgreSQL postgresql>=14.0<14.14
PostgreSQL postgresql>=15.0<15.9
PostgreSQL postgresql>=16.0<16.5
PostgreSQL postgresql=17.0
PostgreSQL postgresql=17.0-beta1
PostgreSQL postgresql=17.0-beta2
PostgreSQL postgresql=17.0-beta3
PostgreSQL postgresql=17.0-rc1
Debian Debian Linux=11.0

Event History

Nov 14, 2024
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·02:01 PM
DescriptionSeverityAffected Software
Dec 2, 2024
Data Sourced
via Launchpad·03:36 PM
Description
Mar 23, 2025
Data Sourced
via Ubuntu·02:57 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-10978?

CVE-2024-10978 has a severity rating that indicates a medium risk due to the potential for incorrect privilege assignment leading to unauthorized data access.

2

How do I fix CVE-2024-10978?

To fix CVE-2024-10978, upgrade to the patched versions of PostgreSQL, which are postgres-13 version 13.18-0+deb11u1 or higher, postgres-15 version 15.10-0+deb12u1 or higher, and make sure other versions are not used.

3

What are the affected versions in CVE-2024-10978?

CVE-2024-10978 affects PostgreSQL versions up to and including 13.16-0+deb11u1, 15.8-0+deb12u1, and 16.4-3.

4

Can CVE-2024-10978 be exploited remotely?

Exploitation of CVE-2024-10978 requires that the attacker have application-level access that enables the use of features like SET ROLE or SET SESSION AUTHORIZATION.

5

What type of vulnerability is CVE-2024-10978?

CVE-2024-10978 is classified as a privilege escalation vulnerability in PostgreSQL.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203