Credential disclosure via unredacted error logging
Published Dec 13, 2023 · Updated May 22, 2025
Sensitive-data logging in Elastic Kibana 7.13.0 through 7.17.15 and 8.0.0 through 8.11.1 allows attackers to read credentials from logs. Unexpected Elasticsearch errors or debug logging serialize unredacted request and error metadata, including authorization headers and policy objects, into Kibana logs. Access to the resulting log records is required; exposed material includes service and end-user credentials, API keys, private keys, tokens, and client secrets.
Summary
What happened
Sensitive-data logging in Elastic Kibana 7.13.0 through 7.17.15 and 8.0.0 through 8.11.1 allows attackers to read credentials from logs. Unexpected Elasticsearch errors or debug logging serialize unredacted request and error metadata, including authorization headers and policy objects, into Kibana logs. Access to the resulting log records is required; exposed material includes service and end-user credentials, API keys, private keys, tokens, and client secrets.
The record
- CVE
- CVE-2023-46675
- Published
- Dec 13, 2023
- Updated
- May 22, 2025
- Vendor
- Elastic
- Product
- Kibana
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2023CVE publishedPublication date reported by the CVE source.
- May 22, 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=7.13.0 <7.17.16
- Affected versionversion=8.0.0 <8.11.2
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