Vulnerability · Published Oct 26, 2023 · Assigned by elastic
CVE-2023-31417Elasticsearch Insertion of sensitive information in audit logs
Medium 4.1
In plain English
A medium-severity sensitive data in logs in Elasticsearch from Elastic. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Maven | org.elasticsearch:elasticsearch | 7.17.13 | GHSA-99pc-69q9-jxf2 |
| Maven | org.elasticsearch:elasticsearch | 8.9.2 | GHSA-99pc-69q9-jxf2 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Elasticsearch | 7.0.0 – before 7.17.128.0.0 – before 8.9.1 |
Weakness: CWE-532 · Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N