First published: Thu Oct 26 2023(Updated: )
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.
Credit: bressers@elastic.co bressers@elastic.co
Affected Software | Affected Version | How to fix |
---|---|---|
>=7.0.0<=7.17.12 | ||
>=8.0.0<=8.9.1 | ||
Elastic Elasticsearch | >=7.0.0<=7.17.12 | |
Elastic Elasticsearch | >=8.0.0<=8.9.1 | |
maven/org.elasticsearch:elasticsearch | >=8.0.0<8.9.2 | 8.9.2 |
maven/org.elasticsearch:elasticsearch | >=7.0.0<7.17.13 | 7.17.13 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Elasticsearch vulnerability is CVE-2023-31417.
The title of this Elasticsearch vulnerability is 'Elasticsearch Insertion of sensitive information in audit logs'.
The impact of this Elasticsearch vulnerability is the insertion of sensitive information, such as passwords, in audit logs.
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.
The severity of this Elasticsearch vulnerability is medium, with a severity value of 4.1.
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.