Spring Integration ZipFramework / library · VMware
CVE-2021-22114
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 · uneditedAddresses partial fix in CVE-2018-1263. Spring-integration-zip, versions prior to 1.0.4, exposes an arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar, xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder.
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 confidenceSpring-integration-zip versions prior to 1.0.4 contains a path traversal vulnerability allowing arbitrary file writes. Attackers craft archives (zip, bzip2, tar, xz, war, cpio, 7z) with filenames containing traversal sequences (e.g., ../../../etc/passwd) that escape the intended extraction directory when unpacked.
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
Spring Integration ZipFramework / library
< 1.0.4CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the spring-integration-zip library in your projectSearch your project dependencies (Maven pom.xml, Gradle build.gradle, or the lib/ directory) for spring-integration-zip or org.springframework.integration.zipAffected if The library is present in your dependencies
-
Determine the installed versionCheck the version declared in your build file or inspect the JAR file manifest (META-INF/MANIFEST.MF) for the Implementation-Version attributeAffected if The version is below 1.0.4 (for example, 1.0.3, 1.0.2, 1.0.1, or 1.0.0)
-
Identify usage of archive extraction featuresSearch your codebase for usage of ZipTransformer, UnZipTransformer, or any custom code that uses Spring Integration zip components to unpack archivesAffected if Your code unpacks zip, bzip2, tar, xz, war, cpio, or 7z files using this library
-
Verify archive handling without path validationReview the extraction logic to confirm whether the application validates or sanitizes entry filenames before writing files to diskAffected if Archive entries are written without validating that filenames do not contain traversal sequences like ../
You are affected if your project includes spring-integration-zip version 1.0.3 or earlier AND uses it to unpack user-supplied or untrusted archives.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.0.4
Upgrade spring-integration-zip to version 1.0.4 or later, which includes the complete fix for CVE-2018-1263.
Fix this in Spring Integration Zip
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22114 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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