Credential disclosure via unredacted debug headers
Published May 4, 2023 · Updated Jan 29, 2025
Information exposure in Elastic Filebeat 7.17.9 and earlier and 8.6.2 allows local users to read HTTP authentication headers from debug logs. The httpjson input's debug logging writes Authorization and Proxy-Authorization request-header contents without redaction. Debug logging must be enabled, and the attacker must have local log access; exposure is limited to credentials carried in those headers.
Summary
What happened
Information exposure in Elastic Filebeat 7.17.9 and earlier and 8.6.2 allows local users to read HTTP authentication headers from debug logs. The httpjson input's debug logging writes Authorization and Proxy-Authorization request-header contents without redaction. Debug logging must be enabled, and the attacker must have local log access; exposure is limited to credentials carried in those headers.
The record
- CVE
- CVE-2023-31413
- Published
- May 4, 2023
- Updated
- Jan 29, 2025
- Vendor
- Elastic
- Product
- Filebeat
- Classifications
- T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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=versions through 7.17.9 and 8.6.2
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