CVE-2023-31417: Elasticsearch Insertion of sensitive information in audit logs
Elasticsearch could allow a local authenticated attacker to obtain sensitive information, caused by the insertion of sensitive information into the log files. By leveraging the deprecated xpack/security API, an attacker could exploit this vulnerability to obtain sensitive information, and use this information to launch further attacks against the affected system.
Other sources
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 Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this Elasticsearch vulnerability?
The vulnerability ID for this Elasticsearch vulnerability is CVE-2023-31417.
What is the title of this Elasticsearch vulnerability?
The title of this Elasticsearch vulnerability is 'Elasticsearch Insertion of sensitive information in audit logs'.
What is the impact of this Elasticsearch vulnerability?
The impact of this Elasticsearch vulnerability is the insertion of sensitive information, such as passwords, in audit logs.
Which software versions are affected by this Elasticsearch vulnerability?
Software versions between 8.0.0 and 8.9.2, and between 7.0.0 and 7.17.13 of the 'org.elasticsearch:elasticsearch' package are affected by this vulnerability.
What is the severity of this Elasticsearch vulnerability?
The severity of this Elasticsearch vulnerability is medium, with a severity value of 4.1.
How can I fix this Elasticsearch vulnerability?
To fix this Elasticsearch vulnerability, you should update the 'org.elasticsearch:elasticsearch' package to version 8.9.2 or 7.17.13, depending on the affected software version.