CVE-2023-49922 Beats Insertion of Sensitive Information into Log File

What is CVE-2023-49922?

CVE-2023-49922 is a medium-severity vulnerability in Elastic Beats, published on 12 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-532

Which versions are affected by CVE-2023-49922?

7 open source packages ship an affected version, including github.com/elastic/beats and github.com/elastic/beats/v7. It affects 1 product.

Products include Elastic Elastic Beats.

How do I fix CVE-2023-49922?

Upgrade github.com/elastic/beats to a fixed version for your release line: 7.17.16 or 8.11.3.

Is CVE-2023-49922 being exploited?

There is no known exploitation of CVE-2023-49922 in the wild and no public exploit code.

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-hj4r-2c9c-29h3, GO-2023-2413, MINI-4m68-7ccj-f3gr, MINI-6mx2-pwmp-p6rh, MINI-754g-3358-cvjv, MINI-8w3r-qvx5-c2jp and 6 more.