CVE-2022-24615: Uncaught Exception in zip4j

CVE-2022-24615 · Severity: low · CVSS 3.1 · Published 2022-02-25

Uncaught Exception in zip4j

Technologies: net.lingala.zip4j:zip4j (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-24615 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-24615 being exploited in the wild.
How severe is CVE-2022-24615?
Low severity, with a CVSS score of 3.1, published 25 February 2022.
Which products and versions are affected?
net.lingala.zip4j:zip4j (Maven) ECOSYSTEM:introduced=0,fixed=2.10.0.
Is there a fix for CVE-2022-24615?
Yes. net.lingala.zip4j:zip4j (Maven): upgrade to 2.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-24615?
Check whether you run net.lingala.zip4j:zip4j (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • net.lingala.zip4j:zip4j (Maven): upgrade to 2.10.0 or later
    # set net.lingala.zip4j:zip4j to 2.10.0 in your pom.xml or build.gradle

Affected products

  • net.lingala.zip4j:zip4j (Maven) ECOSYSTEM:introduced=0,fixed=2.10.0

Identifiers

  • CVE-2022-24615
  • GHSA-q62h-jw38-24vh

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.