CVE-2023-49922

Beats Insertion of Sensitive Information into Log File

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.

Category

6.8
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.44%
Vendor Advisory elastic.co
Affected: Elastic Beats
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2023-49922?
CVE-2023-49922 has been scored as a medium severity vulnerability.
How to fix CVE-2023-49922?
To fix CVE-2023-49922, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-49922 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-49922 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-49922?
CVE-2023-49922 affects Elastic Beats.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.