CVE-2023-49922: Beats Insertion of Sensitive Information into Log File
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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-49922?
CVE-2023-49922 is classified as a moderate severity vulnerability affecting Beats and Elastic Agent.
How do I fix CVE-2023-49922?
To fix CVE-2023-49922, update to Elastic Beats version 7.17.16 or 8.11.3 or newer.
What happens if I don't address CVE-2023-49922?
Failing to address CVE-2023-49922 may lead to unlogged event failures that could impede data ingestion into Elasticsearch.
Which software is affected by CVE-2023-49922?
CVE-2023-49922 affects Elastic Beats versions between 7.0.0 and 7.17.16 as well as 8.0.0 to 8.11.3.
What is the nature of the logging issue in CVE-2023-49922?
The logging issue in CVE-2023-49922 occurs when Beats or Elastic Agent logs raw events at WARN or ERROR levels if ingestion fails with certain 4xx HTTP status codes.