Skip to content

Elastic Beats inserts sensitive information into log file

Moderate severity GitHub Reviewed Published Dec 12, 2023 to the GitHub Advisory Database • Updated Jun 25, 2024

Package

gomod github.com/elastic/beats (Go)

Affected versions

>= 8.0.0, < 8.11.3
>= 7.0.0, < 7.17.16

Patched versions

8.11.3
7.17.16
gomod github.com/elastic/beats/v7 (Go)
>= 7.0.0, < 7.17.16
7.17.16

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.

References

Published by the National Vulnerability Database Dec 12, 2023
Published to the GitHub Advisory Database Dec 12, 2023
Reviewed Dec 19, 2023
Last updated Jun 25, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

0.063%
(29th percentile)

Weaknesses

CVE ID

CVE-2023-49922

GHSA ID

GHSA-hj4r-2c9c-29h3

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.