VulnerabilityPublished 17 Dec 2025Updated 23 Jan 2026

CVE-2024-29371: jose4j · Improper Restriction of Security Token Assignment

Affects jose4jSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.9.6 soon.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.9.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.bitbucket.b_c/jose4j to 0.9.6.

Affected software

Product	Affected	Fixed in
Mavenorg.bitbucket.b_c/jose4j`pkg:maven/org.bitbucket.b_c/jose4j`Other threats	Affected <0.9.6	Fixed in 0.9.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-29371, organizations should immediately upgrade the jose4j library to version 0.9.6 or later, where the vulnerability is fixed. If upgrading is not immediately feasible, implement strict input validation to detect and reject JWE tokens with suspiciously high compression ratios or abnormal sizes before decompression. Employ resource usage limits such as memory and CPU time quotas on processes handling JWE tokens to prevent resource exhaustion. Deploy Web Application Firewalls (WAFs) or API gateways with anomaly detection capabilities to identify and block malformed or malicious tokens. Monitor application logs and system metrics for unusual spikes in resource consumption that could indicate exploitation attempts. Additionally, consider rate limiting requests to endpoints that process JWE tokens to reduce the risk of DoS attacks. Conduct regular security assessments and penetration testing focusing on token processing components. Finally, maintain an incident response plan to quickly address potential DoS incidents related to this vulnerability.

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.

Impact

For European organizations, the primary impact of CVE-2024-29371 is service disruption due to Denial-of-Service attacks. Applications that rely on jose4j for processing JWE tokens—commonly used in secure communications, identity management, and API security—may become unresponsive or crash under attack. This can lead to downtime, loss of business continuity, and degraded user experience. Critical infrastructure or services that depend on these applications could face operational interruptions. Since the vulnerability does not compromise confidentiality or integrity, data breaches are unlikely; however, the availability impact alone can have severe consequences, especially for sectors requiring high uptime such as finance, healthcare, and government services. The ease of exploitation without authentication or user interaction increases the risk of automated attacks targeting exposed endpoints. Additionally, the increased resource consumption could lead to cascading failures in shared hosting or cloud environments, amplifying the impact. European organizations must consider the risk to their service availability and potential reputational damage from prolonged outages.

CWE-1259Improper Restriction of Security Token Assignment (opens in a new tab)
Base weakness
The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.
Architecture and Design · Implementation
Security Token assignment review checks for design inconsistency and common weaknesses.; Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
Exploitation of Improperly Controlled Hardware Security Identifiers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

bitbucket.org/b_c/jose4j/issues/220/vuln-zip-bomb-attack (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jan 2026, 19:19 UTC

WeaknessesCWE-1259

Technical details

References

Community reviews

Related threats