dbcve.org
IvyApplication · Apache

CVE-2022-37865

CRITICAL · 9.1 CVSS v3.1 Published 2022-11-07
Fix available
A fix is available. Upgrade to 2.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Ivy 2.4.0-2.5.0 contains a path traversal vulnerability in its archive extraction feature. When processing artifacts with 'zip', 'jar', or 'war' packaging, Ivy does not validate target paths, allowing malicious archives to contain absolute paths or '..' sequences that write files to arbitrary locations on the filesystem where Ivy has write permissions.

MitigationUpgrade Apache Ivy to version 2.5.1 or later to obtain the path validation fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IvyApplication
Affected:>= 2.4.0, < 2.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ivy version
    Locate the ivy JAR file in your project dependencies or build environment. Check the filename (e.g., ivy-2.4.0.jar) or inspect the JAR manifest for the Implementation-Version attribute using: jar -xf ivy-*.jar META-INF/MANIFEST.MF && cat META-INF/MANIFEST.MF
    Affected if The installed version is 2.4.0 through 2.5.0 (inclusive)
  2. Determine if Ivy processes zip/jar/war artifacts
    Review your Ivy resolve and retrieve operations, or inspect your ivy.xml/ivy-settings.xml files for dependencies with packaging types: <artifact name="..." type="jar"/>, <artifact name="..." type="war"/>, or <artifact name="..." type="zip"/>
    Affected if Ivy is configured to retrieve or cache artifacts with jar, war, or zip packaging types
  3. Verify Ivy's output directory configuration
    Check your ivy.xml, ivy-settings.xml, or Ant build file for the 'pattern' attribute on retrieve or cache operations. Look for dest attribute configurations like: <ivy:retrieve pattern="lib/[artifact].[ext]"/> or check the default ivy cache location (typically ~/.ivy2/cache/)
    Affected if The destination pattern writes to a location accessible by the Ivy process user, enabling arbitrary file write if a malicious artifact is processed
  4. Inspect for existing unexpected files
    Search the filesystem directories where Ivy writes (ivy cache directory, retrieve destinations) for files with absolute paths or suspicious names that do not match expected artifact names. Run: find /path/to/cache -name "*../*" -o -name "/etc/*" -o -name "/tmp/*" (adjust paths to your Ivy output locations)
    Affected if Files exist outside the expected cache/retrieve directory structure, indicating exploitation has occurred

You are affected if Ivy version 2.4.0-2.5.0 is installed AND it processes jar/war/zip artifacts into locations where path traversal could write files outside the intended directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.1 or later
Fixed in 2.5.1
Interim mitigation

Upgrade Apache Ivy to version 2.5.1 or later to obtain the path validation fix.

Recommended fix High confidence

Apache Ivy 2.5.1

  1. Download Apache Ivy 2.5.1 from the official Apache Ivy distribution (https://ant.apache.org/ivy/)
  2. Replace the existing ivy-*.jar file in your project or Ivy installation directory with the new version
  3. If using Ivy as a dependency in a build tool (Maven/Gradle), update the ivy version dependency to 2.5.1
  4. Clear any cached artifacts that may have been previously unpacked to ensure clean state
  5. Verify the upgrade by running your build process and confirming artifact resolution and extraction work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ivy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-37865 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data