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-2019-10199 Vulnerability in maven package org.keycloak:keycloak-services
CVE-2022-0087 Vulnerability in npm package @keystone-6/auth
CVE-2022-34800 Vulnerability in maven package tools.devnull:build-notifications
CVE-2023-40349 Vulnerability in maven package org.jenkins-ci.plugins:gogs-webhook
CVE-2018-1000148 Vulnerability in maven package org.jenkins-ci.plugins:copy-to-slave