CVE-2023-49922 is a medium-severity (CVSS 6.8) CWE-532 vulnerability in github.com/elastic/beats/v7. A fix is available for github.com/elastic/beats/v7 — see the affected versions and patch details below.
Elastic Beats inserts sensitive information into log file
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-49922.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/elastic/beats/v7🐹github.com/elastic/beats🐹github.com/elastic/beatsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/elastic/beats/v7 | ≥ 7.0.0&&< 7.17.16 | 7.17.16go get github.com/elastic/beats/v7@v7.17.16 |
| 🐹Go | github.com/elastic/beats | ≥ 8.0.0&&< 8.11.3 | 8.11.3go get github.com/elastic/beats@v8.11.3 |
| 🐹Go | github.com/elastic/beats | ≥ 7.0.0&&< 7.17.16 | 7.17.16go get github.com/elastic/beats@v7.17.16 |
Affected Products
elastic beatselasticDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/elastic/beats/v7, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/elastic/beats/v7 to 7.17.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49922 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-49922 in your dependencies?
Find it across Go, including transitive dependencies.