First published: Thu 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 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 Software | Affected Version | How to fix |
---|---|---|
PostgreSQL Common | <17.1<16.5<15.9<14.14<13.17<12.21 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2326251 is classified as a privilege escalation vulnerability that can lead to unauthorized access to sensitive data.
To fix REDHAT-BUG-2326251, you should upgrade PostgreSQL to the latest versions beyond those listed as affected.
PostgreSQL versions up to 17.1 and down to 12.21 are affected by REDHAT-BUG-2326251.
An attacker can exploit REDHAT-BUG-2326251 to manipulate or view data in the database by using improper privilege settings.
Yes, exploitation of REDHAT-BUG-2326251 requires the application to utilize SET ROLE, SET SESSION AUTHORIZATION, or a similar feature.