# CVE-2022-37866: Apache Ivy vulnerable to path traversal

Source: https://junglewise.ai/threats/cve-2022-37866-apache-ivy-vulnerable-to-path-traversal  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-11-07  
License: CC BY 4.0 with a link back

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

Apache Ivy vulnerable to path traversal

Technologies: [org.apache.ivy:ivy (Maven)](https://junglewise.ai/threats/technologies/org-apache-ivy-ivy). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2022-37866 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2022-37866 being exploited in the wild.

**How severe is CVE-2022-37866?** 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.0.0,fixed=2.5.1.

**Is there a fix for CVE-2022-37866?** 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-37866?** 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

  ```sh
  # 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.0.0,fixed=2.5.1

## Identifiers

- CVE-2022-37866
- GHSA-wv7w-rj2x-556x

## Related threats

- [Apache Ivy External Entity Reference vulnerability](https://junglewise.ai/threats/cve-2022-46751-apache-ivy-external-entity-reference-vulnerability)
- [Apache Ivy does not verify target path when extracting the archive](https://junglewise.ai/threats/cve-2022-37865-apache-ivy-does-not-verify-target-path-when-extracting-the)