CVE-2023-31417: Elasticsearch allows insertion of sensitive information into log files when using deprecated URIs

CVE-2023-31417 · Severity: low · CVSS 3.1 · Published 2023-10-26

Elasticsearch allows insertion of sensitive information into log files when using deprecated URIs

Technologies: org.elasticsearch:elasticsearch (Maven). Vendors: Maven.

Quick answers

Is CVE-2023-31417 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-31417 being exploited in the wild.
How severe is CVE-2023-31417?
Low severity, with a CVSS score of 3.1, published 26 October 2023.
Which products and versions are affected?
org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.17.13.
Is there a fix for CVE-2023-31417?
Yes. org.elasticsearch:elasticsearch (Maven): upgrade to 7.17.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-31417?
Check whether you run org.elasticsearch:elasticsearch (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.elasticsearch:elasticsearch (Maven): upgrade to 7.17.13 or later
    # set org.elasticsearch:elasticsearch to 7.17.13 in your pom.xml or build.gradle

Affected products

  • org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.17.13

Identifiers

  • CVE-2023-31417
  • GHSA-99pc-69q9-jxf2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.