GHSA-m9jm-rhrm-gcxj
MEDIUMGHSA-m9jm-rhrm-gcxj is a medium-severity (CVSS 4.7) Path Traversal vulnerability in org.springframework.integration:spring-integration-zip. O3 Security confirms whether GHSA-m9jm-rhrm-gcxj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Path traversal in org.springframework.integration:spring-integration-zip
Blast Radius
org.springframework.integration:spring-integration-zipReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring-integration-zip versions prior to 1.0.1 exposes an arbitrary file write vulnerability, which 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.integration:spring-integration-zip | all versions | 1.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.integration:spring-integration-zip. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.integration:spring-integration-zip to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9jm-rhrm-gcxj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m9jm-rhrm-gcxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-m9jm-rhrm-gcxj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m9jm-rhrm-gcxj in your dependencies?
O3 detects GHSA-m9jm-rhrm-gcxj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.