Datastore password disclosure via unredacted parser errors
Published Oct 31, 2023 · Updated Sep 5, 2024
Sensitive data exposure in AuthZed SpiceDB before 1.27.0-rc1 allows local users to read datastore passwords from logs. Datastore initialization returned parser errors containing the entire malformed connection URI, while normal error logging preserved the embedded password. Exploitation requires a malformed configured URI and access to the resulting process logs; the consequence is disclosure of that URI's password.
Summary
What happened
Sensitive data exposure in AuthZed SpiceDB before 1.27.0-rc1 allows local users to read datastore passwords from logs. Datastore initialization returned parser errors containing the entire malformed connection URI, while normal error logging preserved the embedded password. Exploitation requires a malformed configured URI and access to the resulting process logs; the consequence is disclosure of that URI's password.
The record
- CVE
- CVE-2023-46255
- Published
- Oct 31, 2023
- Updated
- Sep 5, 2024
- Vendor
- AuthZed
- Product
- SpiceDB
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 31, 2023CVE publishedPublication date reported by the CVE source.
- Sep 5, 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=< 1.27.0-rc1
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