Vulnerabilities · 2024 · Postgresql
CVE-2024-10978
Postgresql vulnerability
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 products
Postgresql, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.postgresql.org/support/security/CVE-2024-10978/ · Vendor Advisory
- lists.debian.org/debian-lts-announce/2024/11/msg00011.html
- lists.debian.org/debian-lts-announce/2024/11/msg00018.html
- www.postgresql.org/message-id/173171334532.1547978.1518068370217143844%40wrigleys.postgres
- nvd.nist.gov/vuln/detail/CVE-2024-10978
- cve.org/CVERecord?id=CVE-2024-10978
More vulnerabilities in Postgresql products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.