Uncaught Exception in zip4j

published 2022-02-24 4 y ago modified 2026-06-17 4 mo ago also GHSA-q62h-jw38-24vh , EUVD-2022-1146

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 distros 1

maven net.lingala.zip4j:zip4j 2.10.0
zip4j_project zip4j 2.10.0

zip4j Debian 14, Debian 13, Debian 12 2.10.0-1

debian advisories DEBIAN-CVE-2022-24615

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-24615 updated 2026-02-25 cvss 5.5

zip4j: Uncaught exceptions while parsing a specially crafted ZIP file

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:N/A:P
GitHub	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	net.lingala.zip4j:zip4j	<2.10.0	2.10.0

Classification

Weakness

CWE-755 Improper Handling of Exceptional Conditions
CWE-248 Uncaught Exception

References

github.com /srikanth-lingala/zip4j/issues/377
web, issue-tracking, third-party-advisory
github.com /srikanth-lingala/zip4j/issues/418
web, issue-tracking, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2022-24615
advisory
github.com /srikanth-lingala/zip4j
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary