Vulnerabilities · 2023 · Elastic
CVE-2023-31417
Elasticsearch vulnerability
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 products
Elasticsearch. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Elasticsearch runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479 · Vendor Advisory
- www.elastic.co/community/security · Vendor Advisory
- security.netapp.com/advisory/ntap-20231130-0006/ · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2023-31417
- security.netapp.com/advisory/ntap-20231130-0006
- github.com/advisories/GHSA-99pc-69q9-jxf2
- nvd.nist.gov/vuln/detail/CVE-2023-31417
- cve.org/CVERecord?id=CVE-2023-31417
More vulnerabilities in Elastic products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.