Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Elastic Beats | >= 7.0.0, < 7.17.16 |
Related Weaknesses (CWE)
References
- https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-updMitigationVendor Advisory
- https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-updMitigationVendor Advisory
FAQ
What is CVE-2023-49922?
CVE-2023-49922 is a vulnerability with a CVSS score of 6.8 (MEDIUM). 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 st...
How severe is CVE-2023-49922?
CVE-2023-49922 has been rated MEDIUM with a CVSS base score of 6.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-49922?
Check the references section above for vendor advisories and patch information. Affected products include: Elastic Elastic Beats.