CVE-2023-31417GHSA-99PC-69Q9-JXF2BIT-ELASTICSEARCH-2023-31417
Elasticsearch Insertion of sensitive information in audit logs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.17.12, 8.9.1, 7.17.13, 8.9.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Elastic Elasticsearch
From 7.0.0 · fixed in 7.17.12; From 8.0.0 · fixed in 8.9.1
- org.elasticsearch:elasticsearchMaven
From 7.0.0 · fixed in 7.17.13
- org.elasticsearch:elasticsearchMaven
From 8.0.0 · fixed in 8.9.2