PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID
Summary
PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID
Original description
The description as published by the source.
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 packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2024-10978 postgresql14 Fixed in: 14.14-r0
- Debian DEBIAN-CVE-2024-10978 postgresql-13 Fixed in: 13.17-0+deb11u1
References
- advisory postgresql.org
- web lists.debian.org
- web postgresql.org
- web nvd.nist.gov
- web lists.debian.org