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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 4.2, indicating it can be exploited remotely over the network but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 2 products from postgresql, from debian organizations running these solutions should prioritize assessment and patching.
Reported in 2024, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2024-11-14T13:15:04.217
2026-06-17T06:56:49.210
Modified
f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
CVSSv3.1: 4.2 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | postgresql | postgresql | < 12.21 | Yes |
| Application | postgresql | postgresql | < 13.17 | Yes |
| Application | postgresql | postgresql | < 14.14 | Yes |
| Application | postgresql | postgresql | < 15.9 | Yes |
| Application | postgresql | postgresql | < 16.5 | Yes |
| Application | postgresql | postgresql | 17.0 | Yes |
| Application | postgresql | postgresql | 17.0 | Yes |
| Application | postgresql | postgresql | 17.0 | Yes |
| Application | postgresql | postgresql | 17.0 | Yes |
| Application | postgresql | postgresql | 17.0 | Yes |
| Operating System | debian | debian_linux | 11.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For postgresql's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.