Advisory

GHSA-hj4r-2c9c-29h3

Also known as: CVE-2023-49922, GO-2023-2413

Summary

Elastic Beats inserts sensitive information into log file

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-12-12 21:31 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/elastic/beats/v7

Go · All systems

Affected

  • introduced 7.0.0, fixed 7.17.16 (semver)

Fixed versions

7.17.16

Fix

github.com/elastic/beats

Go · All systems

Affected

  • introduced 8.0.0, fixed 8.11.3 (semver)

Fixed versions

8.11.3

Fix

github.com/elastic/beats

Go · All systems

Affected

  • introduced 7.0.0, fixed 7.17.16 (semver)

Fixed versions

7.17.16

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences