Beats Insertion of Sensitive Information into Log File
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Beats 7.17.16, 8.11.3.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Elastic | Beats | >=7.0.0, 8.0.0 <7.17.16, 8.11.3 | 7.17.16, 8.11.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Elastic, strongest first
Embed
A live severity badge for an advisory, README or ticket