CVE-2024-29371: 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 wi
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: libjose4j-java (Debian:13) 0.9.6-1; org.bitbucket.b_c:jose4j (Maven) 0.9.6; eap7-apache-cxf (Red Hat:jboss_enterprise_application_platform_eus:7.3::el7) 0:3.4.10-4.SP2_redhat_00004.1.el7eap.
Low priority for now. Upgrade to libjose4j-java (Debian:13) 0.9.6-1; org.bitbucket.b_c:jose4j (Maven) 0.9.6; eap7-apache-cxf (Red Hat:jboss_enterprise_application_platform_eus:7.3::el7) 0:3.4.10-4.SP2_redhat_00004.1.el7eap or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Dec 17, 2025
- Updated
- Oct 27, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-1259
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jose4j project | jose4j | cpe:2.3:a:jose4j_project:jose4j |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jose4j project jose4jbefore 0.9.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | libjose4j-java | before 0.9.6-1 | 0.9.6-1 |
| Maven | org.bitbucket.b_c:jose4j | before 0.9.6 | 0.9.6 |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-apache-cxf | before 0:3.4.10-4.SP2_redhat_00004.1.el7eap | 0:3.4.10-4.SP2_redhat_00004.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-apache-cxf-rt | before 0:3.4.10-4.SP2_redhat_00004.1.el7eap | 0:3.4.10-4.SP2_redhat_00004.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-apache-cxf-services | before 0:3.4.10-4.SP2_redhat_00004.1.el7eap | 0:3.4.10-4.SP2_redhat_00004.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-apache-cxf-tools | before 0:3.4.10-4.SP2_redhat_00004.1.el7eap | 0:3.4.10-4.SP2_redhat_00004.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-undertow | before 0:2.0.41-8.SP9_redhat_00001.1.el7eap | 0:2.0.41-8.SP9_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-wildfly | before 0:7.3.18-3.GA_redhat_00001.1.el7eap | 0:7.3.18-3.GA_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-wildfly-java-jdk11 | before 0:7.3.18-3.GA_redhat_00001.1.el7eap | 0:7.3.18-3.GA_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-wildfly-java-jdk8 | before 0:7.3.18-3.GA_redhat_00001.1.el7eap | 0:7.3.18-3.GA_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-wildfly-javadocs | before 0:7.3.18-3.GA_redhat_00001.1.el7eap | 0:7.3.18-3.GA_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform_eus:7.3::el7 | eap7-wildfly-modules | before 0:7.3.18-3.GA_redhat_00001.1.el7eap | 0:7.3.18-3.GA_redhat_00001.1.el7eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-cli | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-commons | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-core-client | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-dto | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-hornetq-protocol | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-hqclient-protocol | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-jakarta-client | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-jakarta-ra | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-jakarta-server | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-jakarta-service-extensions | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
| Red Hat:jboss_enterprise_application_platform:8.0::el8 | eap8-activemq-artemis-jdbc-store | before 0:2.21.0-5.redhat_00052.1.el8eap | 0:2.21.0-5.redhat_00052.1.el8eap |
+96
Same product
jose4j project: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-31582jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less.30Monitor
- CVE-2023-51775The jose4j component before 0.9.4 for Java allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count)26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libjose4j-java | 0.9.6-1 · Debian:13 | Package registry (OSV) |
| Maven:org.bitbucket.b_c:jose4j | 0.9.6 | Package registry (OSV) |
| red hat:eap8-apache-commons-beanutils | 0:1.9.4-13.redhat_00004.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-apache-cxf | 0:4.0.4-1.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-apache-cxf-rt | 0:4.0.4-1.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-apache-cxf-services | 0:4.0.4-1.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-apache-cxf-tools | 0:4.0.4-1.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-apache-cxf-xjc-utils | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-codemodel | 0:4.0.5-2.redhat_00001.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-cxf-xjc-boolean | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-cxf-xjc-bug986 | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-cxf-xjc-dv | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-cxf-xjc-runtime | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| red hat:eap8-cxf-xjc-ts | 0:4.0.0-5.redhat_00003.1.el8eap · Red Hat:jboss_enterprise_application_platform:8.0::el8 | Package registry (OSV) |
| suse:suse-manager-5.0-aarch64-proxy-httpd-image | 5.0.7-7.30.13 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-aarch64-proxy-salt-broker-image | 5.0.7-7.32.15 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-aarch64-proxy-squid-image | 5.0.7-7.30.6 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-aarch64-proxy-ssh-image | 5.0.7-7.30.5 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-aarch64-proxy-tftpd-image | 5.0.7-7.30.5 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-ppc64le-proxy-httpd-image | 5.0.7-7.30.13 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-ppc64le-proxy-salt-broker-image | 5.0.7-7.32.15 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-ppc64le-proxy-squid-image | 5.0.7-7.30.6 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-ppc64le-proxy-ssh-image | 5.0.7-7.30.5 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-ppc64le-proxy-tftpd-image | 5.0.7-7.30.5 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-s390x-proxy-httpd-image | 5.0.7-7.30.13 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
| suse:suse-manager-5.0-s390x-proxy-salt-broker-image | 5.0.7-7.32.15 · SUSE:Manager Proxy 5.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1259 · Improper Restriction of Security Token AssignmentCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →