Sensitive-data exposure via raw event error logging
Published Dec 12, 2023 · Updated Dec 2, 2024
Sensitive-data logging in Elastic Beats allows attackers to expose raw event contents when Elasticsearch rejects ingestion with most 4xx errors. The publisher error path records the entire failed event at WARN or ERROR instead of limiting the record to non-sensitive diagnostic context. Exposure requires a rejected event containing private data and access to Beat logs; affected releases are 7.0.0 through 7.17.15 and 8.0.0 through 8.11.2.
Summary
What happened
Sensitive-data logging in Elastic Beats allows attackers to expose raw event contents when Elasticsearch rejects ingestion with most 4xx errors. The publisher error path records the entire failed event at WARN or ERROR instead of limiting the record to non-sensitive diagnostic context. Exposure requires a rejected event containing private data and access to Beat logs; affected releases are 7.0.0 through 7.17.15 and 8.0.0 through 8.11.2.
The record
- CVE
- CVE-2023-49922
- Published
- Dec 12, 2023
- Updated
- Dec 2, 2024
- Vendor
- Elastic
- Product
- Beats
- Classifications
- CWE-532
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2023CVE publishedPublication date reported by the CVE source.
- Dec 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=7.0.0, 8.0.0 <7.17.16, 8.11.3
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