CVE-2023-49922
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.
How to fix
- elastic elastic_beats7.17.16, 8.11.3 or later
- github.com/elastic/beats/v77.17.16 or later
- github.com/elastic/beats8.11.3, 7.17.16 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| elastic elastic_beats | 7.0.0 ≤ v < 7.17.16, 8.0.0 ≤ v < 8.11.3 | 7.17.16, 8.11.3 |
| github.com/elastic/beats/v7Go | 7.0.0 ≤ v < 7.17.16, v < 7.17.16 | 7.17.16 |
| github.com/elastic/beatsGo | 8.0.0 ≤ v < 8.11.3, 7.0.0 ≤ v < 7.17.16 | 8.11.3, 7.17.16 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.