CVE-2022-24615 — zip4j
MEDIUMCVE-2022-24615 is a medium-severity (CVSS 5.5) CWE-755 vulnerability in net.lingala.zip4j:zip4j. A fix is available for net.lingala.zip4j:zip4j — see the affected versions and patch details below.
Uncaught Exception in zip4j
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
net.lingala.zip4j:zip4jReal-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
zip4j up to v2.10.0 can throw various uncaught exceptions while parsing a specially crafted ZIP file, which could result in an application crash. This could be used to mount a denial of service attack against services that use zip4j library.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.lingala.zip4j:zip4j | all versions | 2.10.0net.lingala.zip4j:zip4j:2.10.0 |
Affected Products
zip4jzip4j_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.lingala.zip4j:zip4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.lingala.zip4j:zip4j to 2.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24615 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-24615 in your dependencies?
Find it across Maven, including transitive dependencies.