CVE-2023-49922
Elastic Beats inserts sensitive information into log file
Record from NVD · Published December 12, 2023
github.com/elastic/beats/v7 is fixed in v7.17.16 and 7.17.16 (Go Modules)
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.
EPSS 0.67% · 52.8th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| github.com/elastic/beats/v7 | Go Modules | v7.17.16, 7.17.16 |
| github.com/elastic/beats | Go Modules | 8.11.3, 7.17.16 |
| apm-server-9.1 | Chainguard | 9.1.10-r10 |
| cloudbeat-fips-8.17 | Chainguard | 8.17.10-r32 |
| apm-server-fips-9.3 | Chainguard | 9.3.7-r0 |
| apm-server-fips-9.1 | Chainguard | 9.1.10-r12 |
| elastic-agent-9.2 | Chainguard | 9.2.8-r12 |
| cloudbeat-8.17 | Chainguard | 8.17.10-r27 |
| apm-server-9.3 | Chainguard | 9.3.7-r0 |
| elastic-agent-fips-9.2 | Chainguard | 9.2.8-r9 |
| elastic-agent-9.1 | Chainguard | 9.1.10-r17 |
| elastic-agent-fips-9.1 | Chainguard | 9.1.10-r18 |
5 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| elastic | elastic_beats | 7.0.0, 8.0.0 |
Timeline
- Dec 12, 2023 CVE Published
- Dec 13, 2023 EPSS Score (30 in total, the first dated here)
- Mar 18, 2026 Security Advisory
- Jun 17, 2026 CVE Updated
- Jul 30, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-49922
vulnetix vdb fixes CVE-2023-49922
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-49922/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart