CVE-2024-29371

Exp

In jose4j before 0.9.6, an attacker can cause a Denial-of-Service (DoS) condition by crafting a malicious JSON Web Encryption (JWE) token with an exceptionally high compression ratio. When this token is processed by the server, it results in significant memory allocation and processing time during decompression.

Published: 2025-12-17 Last update: 2026-01-23 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-29371 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2024-29371

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-29371

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-12-18 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-29371

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-29371

GitHub Security Advisory for CVE-2024-29371

GHSA-3677-xxcr-wjqv · Severity: high · Ecosystem: maven — jose4j is vulnerable to DoS via compressed JWE content

OS Trackers for CVE-2024-29371

vendor priority summary link
debian not yet assigned CVE-2024-29371 not yet assigned priority: Debian including 1 source packages (libjose4j-java), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2024-29371
redhat high — https://access.redhat.com/security/cve/CVE-2024-29371
suse high — https://www.suse.com/security/cve/CVE-2024-29371/
ubuntu medium CVE-2024-29371 medium priority: Ubuntu including 1 source packages (libjose4j-java), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): needs-triage 4, ignored 1. https://ubuntu.com/security/CVE-2024-29371

Affected software / configurations for CVE-2024-29371

Vendor Product Version Raw CPE
jose4j_project jose4j < 0.9.5 cpe:2.3:a:jose4j_project:jose4j:*:*:*:*:*:*:*:*

References for CVE-2024-29371

URL Tags
https://bitbucket.org/b_c/jose4j/issues/220/vuln-zip-bomb-attack Exploit Issue Tracking Mitigation
cvelogic Threat Intelligence