Skip to content

Apache Ivy does not verify target path when extracting the archive

Critical severity GitHub Reviewed Published Nov 7, 2022 to the GitHub Advisory Database • Updated Jul 5, 2023

Package

maven org.apache.ivy:ivy (Maven)

Affected versions

>= 2.4.0, < 2.5.1

Patched versions

2.5.1

Description

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 version 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 version 2.5.1.

References

Published by the National Vulnerability Database Nov 7, 2022
Published to the GitHub Advisory Database Nov 7, 2022
Reviewed Nov 7, 2022
Last updated Jul 5, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS score

0.123%
(48th percentile)

Weaknesses

CVE ID

CVE-2022-37865

GHSA ID

GHSA-94rr-4jr5-9h2p

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.