Vulnerability 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 Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Elastic | Elasticsearch | >= 7.0.0, <= 7.17.12 |
Related Weaknesses (CWE)
References
- https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342Vendor 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/342Vendor Advisory
- https://security.netapp.com/advisory/ntap-20231130-0006/Third Party Advisory
- https://www.elastic.co/community/securityVendor Advisory
FAQ
What is CVE-2023-31417?
CVE-2023-31417 is a vulnerability with a CVSS score of 4.1 (MEDIUM). 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 d...
How severe is CVE-2023-31417?
CVE-2023-31417 has been rated MEDIUM with a CVSS base score of 4.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-31417?
Check the references section above for vendor advisories and patch information. Affected products include: Elastic Elasticsearch.