CVE-2024-29371 — jose4j
HIGHCVE-2024-29371 is a high-severity (CVSS 7.5) CWE-1259 vulnerability in org.bitbucket.b_c:jose4j. A fix is available for org.bitbucket.b_c:jose4j — see the affected versions and patch details below.
jose4j is vulnerable to DoS via compressed JWE content
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-29371.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.bitbucket.b_c:jose4jReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.bitbucket.b_c:jose4j | all versions | 0.9.6org.bitbucket.b_c:jose4j:0.9.6 |
Affected Products
jose4jjose4j_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bitbucket.b_c:jose4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.bitbucket.b_c:jose4j to 0.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-29371 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated Important as it can lead to a Denial of Service in applications that process untrusted JSON Web Encryption tokens. An attacker can craft a malicious JWE token with an exceptionally high compression ratio, causing excessive memory allocation and processing time during decompression in…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap | RHSA-2026:33371 |
| Red Hat JBoss Enterprise Application Platform 8 | see advisory | RHSA-2024:5482 |
| Red Hat JBoss Enterprise Application Platform 8.1.0 | org.bitbucket.b_c/jose4j:0.9.6.redhat-00001 | RHSA-2025:17299 |
| Streams for Apache Kafka 2.9.4 | jose4j | RHSA-2026:34608 |
| Streams for Apache Kafka 3.2.0 | jose4j | RHSA-2026:13571 |
| OpenShift Developer Tools and Services 4.12 | ocp-tools-4/jenkins-rhel8:1776764096 | RHSA-2026:10209 |
| OpenShift Developer Tools and Services 4.12 | ocp-tools-4/jenkins-rhel8:1786628667 | RHSA-2026:60247 |
| OpenShift Developer Tools and Services 4.13 | ocp-tools-4/jenkins-rhel8:1776764096 | RHSA-2026:10201 |
Frequently Asked Questions
Is CVE-2024-29371 in your dependencies?
Find it across Maven, including transitive dependencies.