Local disclosure and code execution via inherited ACLs
Published Mar 19, 2021 · Updated Aug 4, 2024
Improper access control in EDB-supplied PostgreSQL 11.0 through 11.2 on Windows allows local users to read database files. The installer leaves inherited ACLs on the binary installation and data directories instead of restricting them to trusted accounts. A Windows account is enough for file reads; with both an unprivileged Windows account and PostgreSQL account in plausible non-default configurations, attackers can make the service account execute arbitrary code.
Summary
What happened
Improper access control in EDB-supplied PostgreSQL 11.0 through 11.2 on Windows allows local users to read database files. The installer leaves inherited ACLs on the binary installation and data directories instead of restricting them to trusted accounts. A Windows account is enough for file reads; with both an unprivileged Windows account and PostgreSQL account in plausible non-default configurations, attackers can make the service account execute arbitrary code.
The record
- CVE
- CVE-2019-10128
- Published
- Mar 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- PostgreSQL Global Development Group
- Product
- PostgreSQL
- Classifications
- CWE-284
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=11.x prior to 11.3
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