CVE-2022-24615

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.

Published: 2022-02-24 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-24615 is rated Low Risk (39.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.28%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-24615

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.14% 0.28% +0.14%
2 2025-11-18 0.27% 0.14% -0.13%
3 2025-04-18 — 0.27% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-24615

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2022-24615

GitHub Security Advisory for CVE-2022-24615

OS Trackers for CVE-2022-24615

vendor priority summary link
debian not yet assigned CVE-2022-24615 not yet assigned priority: Debian including 1 source packages (zip4j), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2022-24615
redhat low — https://access.redhat.com/security/cve/CVE-2022-24615
ubuntu low CVE-2022-24615 low priority: Ubuntu including 1 source packages (zip4j), 13 status rows across 13 suites (focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 8, needs-triage 5. https://ubuntu.com/security/CVE-2022-24615

Affected software / configurations for CVE-2022-24615

Vendor Product Version Raw CPE
zip4j_project zip4j < 2.10.0 cpe:2.3:a:zip4j_project:zip4j:*:*:*:*:*:*:*:*

References for CVE-2022-24615

URL Tags
https://github.com/srikanth-lingala/zip4j/issues/377 Issue Tracking Third Party Advisory
https://github.com/srikanth-lingala/zip4j/issues/418 Issue Tracking Third Party Advisory
cvelogic Threat Intelligence