A vulnerability was found in Elastic Agent up to 7.17.15/8.11.2. It has been classified as problematic. This affects an unknown code block of the component HTTP Status Code Handler. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. The summary by CVE is:

An issue was discovered by Elastic whereby 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 Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the 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.

The weakness was presented 12/12/2023. It is possible to read the advisory at discuss.elastic.co. This vulnerability is uniquely identified as CVE-2023-6687 since 12/11/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 7.17.16 or 8.11.3 eliminates this vulnerability.

See VDB-247622 for similar entry.

Productinfo

Vendor

• Elastic

Name

• Agent

Version

• 7.17.0
• 7.17.1
• 7.17.2
• 7.17.3
• 7.17.4
• 7.17.5
• 7.17.6
• 7.17.7
• 7.17.8
• 7.17.9
• 7.17.10
• 7.17.11
• 7.17.12
• 7.17.13
• 7.17.14
• 7.17.15
• 8.11.0
• 8.11.1
• 8.11.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion