Skip to content
Fencer Intel
critical 9.1

CVE-2022-37865 json

Apache Ivy allows creating/overwriting any file on the system

published 4y ago modified 4mo ago also GHSA-94rr-4jr5-9h2p , EUVD-2022-7292

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

With Apache Ivy 2.4.0 an optional packaging attribute has been introduced that allows artifacts to be unpacked on the fly if they used pack200 or zip packaging. For artifacts using the "zip", "jar" or "war" packaging Ivy prior to 2.5.1 doesn't verify the target path when extracting the archive. An archive containing absolute paths or paths that try to traverse "upwards" using ".." sequences can then write files to any location on the local fie system that the user executing Ivy has write access to. Ivy users of version 2.4.0 to 2.5.0 should upgrade to Ivy 2.5.1.

Patch / fix

  • maven org.apache.ivy:ivy 2.5.1
  • apache ivy 2.5.1
  • apache-ivy openSUSE Tumbleweed 2.5.1-1.1

opensuse advisories openSUSE-SU-2024:12506-1

Is CVE-2022-37865 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-37865 updated cvss 9.1

apache-ivy: Directory Traversal

  • Red Hat Migration Toolkit for Applications 6 apache-ivy Red Hat Migration Toolkit for Runtimes org.freemarker-freemarker-2.3.31.redhat_00001-1
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 apache-ivy, apache-ivy-javadoc Red Hat Fuse 7 apache-ivy
    affected: no fix planned “Out of support scope”
  • Red Hat Integration Camel K 1 apache-ivy
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Data Grid 7 apache-ivy Red Hat JBoss Enterprise Application Platform 6 apache-ivy
    affected: no fix planned “Out of support scope”
  • Red Hat Software Collections rh-maven36-apache-ivy, rh-maven36-apache-ivy-javadoc
    affected: no fix planned “Will not fix”
  • Red Hat RHINT Camel-Springboot 3.20.1
    fixed: vendor fix RHSA-2023:2100
  • Red Hat A-MQ Clients 2 apache-ivy Red Hat Data Grid 8 apache-ivy Red Hat Integration Camel Quarkus 1 apache-ivy Red Hat JBoss Enterprise Application Platform 7 apache-ivy Red Hat JBoss Enterprise Application Platform Expansion Pack apache-ivy Red Hat OpenShift Application Runtimes apache-ivy
    +1 more products
    Red Hat Single Sign-On 7 apache-ivy
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

2.14% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.ivy:ivy
>=2.4.0, <2.5.1
2.5.1

Affected products

  • Apache Software Foundation Apache Ivy

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.