dbcve.org
IvyApplication · Apache

CVE-2022-37866

HIGH · 7.5 CVSS v3.1 Published 2022-11-07
Fix available
A fix is available. Upgrade to 2.5.1 or later.
See remediation →
84/100
Remediation priority · High
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
When Apache Ivy downloads artifacts from a repository it stores them in the local file system based on a user-supplied "pattern" that may include placeholders for artifacts coordinates like the organisation, module or version. If said coordinates contain "../" sequences - which are valid characters for Ivy coordinates in general - it is possible the artifacts are stored outside of Ivy's local cache or repository or can overwrite different artifacts inside of the local cache. In order to exploit this vulnerability an attacker needs collaboration by the remote repository as Ivy will issue http requests containing ".." sequences and a "normal" repository will not interpret them as part of the artifact coordinates. Users of Apache Ivy 2.0.0 to 2.5.1 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 is vulnerable to path traversal when downloading artifacts. The software uses user-supplied patterns with artifact coordinates (organisation, module, version) to determine local file storage locations. If these coordinates contain '../' sequences - which are valid in Ivy coordinates - an attacker can cause artifacts to be written outside the intended cache directory or overwrite unrelated cached artifacts. Exploitation requires a malicious or colluding remote repository since normal repositories don't pass '..' sequences through as artifact coordinates.

MitigationUpgrade to Apache Ivy 2.5.1 or later. Additionally, review and validate that repository configurations and artifact patterns do not permit unexpected directory traversal.

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.0.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
None

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

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 Apache Ivy version
    Locate the ivy JAR file in your project or installation and check its version (for example, by examining the JAR filename, running 'java -jar ivy.jar -version', or inspecting the MANIFEST.MF file inside the JAR).
    Affected if The version is 2.0.0 or higher but lower than 2.5.1.
  2. Locate Ivy settings file
    Find the ivysettings.xml file used by your build (commonly in the project root, conf directory, or referenced via the ivy.settings system property).
    Affected if A custom ivysettings.xml file exists that references external or untrusted repositories.
  3. Review artifact pattern configuration
    Inspect the ivysettings.xml and any ivy.xml files for artifact and resolver patterns, specifically looking for patterns that incorporate organisation, module, or version variables (for example, '${ivy.cache.dir}/[organisation]/[module]/[type]/[artifact].[ext]').
    Affected if Artifact patterns allow user-controlled organisation or module names to directly influence file paths without sanitization.
  4. Check repository trust configuration
    Examine the resolver configurations in ivysettings.xml to identify which repositories are configured and whether any are external, community-hosted, or otherwise untrusted.
    Affected if The configuration includes external or third-party repositories that could supply malicious artifact coordinates containing '../' sequences.
  5. Inspect cache directory permissions
    Verify the ivy cache directory location (typically set via ivy.cache.dir in ivysettings.xml or defaulting to user home/.ivy2/cache) and check file permissions.
    Affected if The cache is writable and shared across untrusted users or projects.

Your environment is affected if Apache Ivy version 2.0.0 through 2.5.0 is in use AND you configure artifact patterns that incorporate untrusted repository-supplied coordinates into filesystem paths.

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 to Apache Ivy 2.5.1 or later. Additionally, review and validate that repository configurations and artifact patterns do not permit unexpected directory traversal.

Recommended fix High confidence

Ivy 2.5.1

  1. Download Apache Ivy 2.5.1 from the official Apache repository (https://archive.apache.org/dist/ant/ivy/)
  2. Replace the existing Ivy installation with version 2.5.1
  3. Verify the upgrade by running 'ivy -version' and confirming it shows 2.5.1

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37866 — 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-37866 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