Unauthorized row access via stale inlined policies
Published Jun 9, 2023 · Updated Jan 6, 2025
Row-level security bypass in PostgreSQL 11 through 15 allows remote authenticated users to read or modify forbidden rows via cached plans. The planner can inline a set-returning SQL function and then reuse its cached plan under a different role without reapplying role-specific row policies. Exposure requires CREATE POLICY plus a security-definer function or plan reuse across SET ROLE operations.
Summary
What happened
Row-level security bypass in PostgreSQL 11 through 15 allows remote authenticated users to read or modify forbidden rows via cached plans. The planner can inline a set-returning SQL function and then reuse its cached plan under a different role without reapplying role-specific row policies. Exposure requires CREATE POLICY plus a security-definer function or plan reuse across SET ROLE operations.
The record
- CVE
- CVE-2023-2455
- Published
- Jun 9, 2023
- Updated
- Jan 6, 2025
- Vendor
- PostgreSQL Global Development Group
- Product
- PostgreSQL
- Classifications
- CWE-20, T1213.006, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo