CVE-2023-49922

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

Configuration 1 (hide)

OR cpe:2.3:a:elastic:elastic_beats:*:*:*:*:*:*:*:*
cpe:2.3:a:elastic:elastic_beats:*:*:*:*:*:*:*:*

History

19 Dec 2023, 15:11

Type Values Removed Values Added
References () https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-update-esa-2023-30/349180 - () https://discuss.elastic.co/t/beats-and-elastic-agent-8-11-3-7-17-16-security-update-esa-2023-30/349180 - Mitigation, Vendor Advisory
First Time Elastic
Elastic elastic Beats
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 6.5
CPE cpe:2.3:a:elastic:elastic_beats:*:*:*:*:*:*:*:*
CWE CWE-532

12 Dec 2023, 20:20

Type Values Removed Values Added
New CVE

Information

Published : 2023-12-12 19:15

Updated : 2024-02-28 20:54


NVD link : CVE-2023-49922

Mitre link : CVE-2023-49922

CVE.ORG link : CVE-2023-49922


JSON object : View

Products Affected

elastic

  • elastic_beats
CWE
CWE-532

Insertion of Sensitive Information into Log File