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.
Remediation
References
https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479
https://security.netapp.com/advisory/ntap-20231130-0006/
https://www.elastic.co/community/security
Related Vulnerabilities
CVE-2014-0363 Vulnerability in maven package org.igniterealtime.smack:smack-core
CVE-2022-29253 Vulnerability in maven package org.xwiki.platform:xwiki-platform-oldcore
CVE-2022-0613 Vulnerability in npm package urijs
CVE-2019-1003055 Vulnerability in maven package org.jvnet.hudson.plugins:ftppublisher
CVE-2021-44548 Vulnerability in maven package org.apache.solr:solr-core