CVE-2022-37865: Apache Ivy does not verify target path when extracting the archive

CVE-2022-37865 · Severity: low · CVSS 3.1 · Published 2022-11-07

Apache Ivy does not verify target path when extracting the archive

Technologies: org.apache.ivy:ivy (Maven). Vendors: Maven.

Quick answers

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

Affected products

  • org.apache.ivy:ivy (Maven) ECOSYSTEM:introduced=2.4.0,fixed=2.5.1

Identifiers

  • CVE-2022-37865
  • GHSA-94rr-4jr5-9h2p

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