cve.bz

CVE-2023-49922 elastic elastic beats

6.5 mediumEPSS 0.7%Fix available

Medium (6.5) in elastic elastic beats. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/elastic/beats/v7 7.17.16.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-12-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-49922 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-49922?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-49922?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-49922 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elastic Beatsfrom 7.0.0, 8.0.0 before 7.17.16, 8.11.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hj4r-2c9c-29h3Gogithub.com/elastic/beats/v7>=7.0.0 <7.17.167.17.16
GHSA-hj4r-2c9c-29h3Gogithub.com/elastic/beats>=8.0.0 <8.11.38.11.3
GHSA-hj4r-2c9c-29h3Gogithub.com/elastic/beats>=7.0.0 <7.17.167.17.16
GO-2023-2413Gogithub.com/elastic/beats/v7<7.17.167.17.16

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON