Sensitive-data exposure via JSON log serialization
Published Nov 15, 2023 · Updated Feb 13, 2025
Sensitive-data exposure in Elastic Logstash 8.10.0 through 8.11.0 allows local users to read keystore-backed secrets from JSON logs. The JSON logging path writes representations of protected SafeURI and Password objects into log records instead of preserving their redacted forms. Exposure requires the non-default JSON log format and a keystore secret referenced by configuration; leaked credentials can grant access to connected services.
Summary
What happened
Sensitive-data exposure in Elastic Logstash 8.10.0 through 8.11.0 allows local users to read keystore-backed secrets from JSON logs. The JSON logging path writes representations of protected SafeURI and Password objects into log records instead of preserving their redacted forms. Exposure requires the non-default JSON log format and a keystore secret referenced by configuration; leaked credentials can grant access to connected services.
The record
- CVE
- CVE-2023-46672
- Published
- Nov 15, 2023
- Updated
- Feb 13, 2025
- Vendor
- Elastic
- Product
- Logstash
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=8.10.0 <8.11.1
What conditions does exploitation require?
What is affected?
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