CVE-2021-39231: Exposure of sensitive information in Apache Ozone

CVE-2021-39231 · Severity: low · CVSS 3.1 · Published 2021-11-23

Exposure of sensitive information in Apache Ozone

Technologies: org.apache.ozone:ozone-main (Maven). Vendors: Maven.

Quick answers

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

Affected products

  • org.apache.ozone:ozone-main (Maven) ECOSYSTEM:introduced=0,fixed=1.2.0

Identifiers

  • CVE-2021-39231
  • GHSA-3w5h-x4rh-hc28

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