Credential exposure via unredacted error logging
Published Dec 13, 2023 · Updated Aug 2, 2024
Sensitive-data logging in Elastic Kibana 8.0.0 through 8.11.0 allows remote authenticated users to expose credentials in error logs. When Elasticsearch returns circuit-breaker or no-shard errors, Kibana records error messages with unredacted request headers, including authorization material. User interaction and an unhealthy cluster are required; anyone able to read the affected logs can recover Kibana system, API, or end-user credentials.
Summary
What happened
Sensitive-data logging in Elastic Kibana 8.0.0 through 8.11.0 allows remote authenticated users to expose credentials in error logs. When Elasticsearch returns circuit-breaker or no-shard errors, Kibana records error messages with unredacted request headers, including authorization material. User interaction and an unhealthy cluster are required; anyone able to read the affected logs can recover Kibana system, API, or end-user credentials.
The record
- CVE
- CVE-2023-46671
- Published
- Dec 13, 2023
- Updated
- Aug 2, 2024
- Vendor
- Elastic
- Product
- Kibana
- Classifications
- CWE-532, T1552.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=8.0.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