Elasticsearch Insertion of sensitive information in audit logs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Elasticsearch 7.17.12 and Elasticsearch 8.9.1.
Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Elastic | Elasticsearch | >=7.0.0 <7.17.12, >=8.0.0 <8.9.1 | 7.17.12, 8.9.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Elasticsearch, strongest first
Embed
A live severity badge for an advisory, README or ticket