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-10325 Vulnerability in maven package io.jenkins.plugins:warnings-ng
CVE-2022-36916 Vulnerability in maven package org.jenkins-ci.plugins:google-cloud-backup
CVE-2017-8032 Vulnerability in maven package org.cloudfoundry.identity:cloudfoundry-identity-uaa
CVE-2010-3863 Vulnerability in maven package org.jsecurity:jsecurity
CVE-2022-36881 Vulnerability in maven package org.jenkins-ci.plugins:git-client