CVE-2023-31417
Elasticsearch generally filters out sensitive information and credentials before logging to the audit log.
Does this matter?
Lower severity and a low EPSS score (0.24%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 4.4 MEDIUMCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.24% probability · 15th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-532
- Affected
- elastic/elasticsearch
- Source
- security@elastic.co
References
- https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479Vendor Advisory
- https://security.netapp.com/advisory/ntap-20231130-0006/Third Party Advisory
- https://www.elastic.co/community/securityVendor Advisory
- https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479Vendor Advisory
- https://security.netapp.com/advisory/ntap-20231130-0006/Third Party Advisory
- https://www.elastic.co/community/securityVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.