github.com/elastic/beats/v7
Affected
- introduced
7.0.0, fixed7.17.16(semver)
Fixed versions
7.17.16
Fix
- Fixed version
7.17.16go get github.com/elastic/beats/[email protected]
Advisory
Also known as: CVE-2023-49922, GO-2023-2413
Elastic Beats inserts sensitive information into log file
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.
Medium Basis: The source's own band: MODERATE
7.0.0, fixed 7.17.16 (semver)7.17.16
7.17.16go get github.com/elastic/beats/[email protected]8.0.0, fixed 8.11.3 (semver)8.11.3
8.11.3go get github.com/elastic/[email protected]7.0.0, fixed 7.17.16 (semver)7.17.16
7.17.16go get github.com/elastic/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0