CVE-2023-31417

Medium

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.

SeverityMedium
CVSS4.1
Exploit probability—
ProductElasticsearch
PublishedOct 26, 2023
First seenOct 26, 2023
Weakness typeCWE-532CWE-532

How to fix

Update
  • org.elasticsearch:elasticsearch7.17.13, 8.9.2 or later

Affected products

ProductAffected versionsFixed in
elastic elasticsearch7.0.0 ≤ v ≤ 7.17.12, 8.0.0 ≤ v ≤ 8.9.1—
org.elasticsearch:elasticsearchMaven7.0.0 ≤ v < 7.17.13, 8.0.0 ≤ v < 8.9.27.17.13, 8.9.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2023-31417 · Elasticsearch · Dark Radar