CVE-2020-7021: Insertion of Sensitive Information into Log File in Elasticsearch

CVE-2020-7021 · Severity: low · CVSS 3.1 · Published 2022-05-24

Insertion of Sensitive Information into Log File in Elasticsearch

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

Quick answers

Is CVE-2020-7021 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-7021 being exploited in the wild.
How severe is CVE-2020-7021?
Low severity, with a CVSS score of 3.1, published 24 May 2022.
Which products and versions are affected?
org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=6.8.14.
Is there a fix for CVE-2020-7021?
Yes. org.elasticsearch:elasticsearch (Maven): upgrade to 6.8.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-7021?
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 6.8.14 or later
    # set org.elasticsearch:elasticsearch to 6.8.14 in your pom.xml or build.gradle

Affected products

  • org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=6.8.14

Identifiers

  • CVE-2020-7021
  • GHSA-cqgv-256r-m9r8

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