CVE-2024-29371 jose4j is vulnerable to DoS via compressed JWE content
High 7.5
Published
Updated
Check this codebase for CVE-2024-29371 and fix it if it is affected.
What it is: CVE-2024-29371 is a high-severity denial of service vulnerability in n/a, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29371 exists.
Affected packages and fixed versions:
- org.bitbucket.b_c:jose4j (Maven): affected all versions; fixed in 0.9.6
- org.bitbucket.b_c:jose4j (Maven): affected all versions; fixed in 0.9.6
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2024-29371/ (Markdown: https://insights.sbomify.com/CVE-2024-29371/index.md)
Attackers can cause denial of service in applications using jose4j by sending malicious JWE tokens with high compression ratios.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-29371?
CVE-2024-29371 is a high-severity denial of service vulnerability in n/a, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-1259
Which versions are affected by CVE-2024-29371?
2 open source packages ship an affected version, including org.bitbucket.b_c:jose4j. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.bitbucket.b_c:jose4j Maven | All versions | 0.9.6 |
org.bitbucket.b_c:jose4j Maven | All versions | 0.9.6 |
Linux distribution packages (38)
suse-manager-5.0-aarch64-proxy-httpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-aarch64-proxy-salt-broker-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-aarch64-proxy-squid-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-aarch64-proxy-ssh-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-aarch64-proxy-tftpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-ppc64le-proxy-httpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-ppc64le-proxy-salt-broker-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-ppc64le-proxy-squid-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-ppc64le-proxy-ssh-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-ppc64le-proxy-tftpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-s390x-proxy-httpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-s390x-proxy-salt-broker-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-s390x-proxy-squid-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-s390x-proxy-ssh-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-s390x-proxy-tftpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-x86_64-proxy-httpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-x86_64-proxy-salt-broker-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-x86_64-proxy-squid-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-x86_64-proxy-ssh-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-x86_64-proxy-tftpd-image SUSE:Manager Proxy 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-aarch64-proxy-httpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-aarch64-proxy-salt-broker-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-aarch64-proxy-squid-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-aarch64-proxy-ssh-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-aarch64-proxy-tftpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-ppc64le-proxy-httpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-ppc64le-proxy-salt-broker-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-ppc64le-proxy-squid-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-ppc64le-proxy-ssh-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-ppc64le-proxy-tftpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-s390x-proxy-httpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-s390x-proxy-salt-broker-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-s390x-proxy-squid-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.6 |
suse-manager-5.0-s390x-proxy-ssh-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-s390x-proxy-tftpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.5 |
suse-manager-5.0-x86_64-proxy-httpd-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.13 |
suse-manager-5.0-x86_64-proxy-salt-broker-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.32.15 |
suse-manager-5.0-x86_64-proxy-squid-image SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.7-7.30.6 |
Products include Jose4j Project Jose4j.
How do I fix CVE-2024-29371?
Upgrade org.bitbucket.b_c:jose4j to 0.9.6 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2024-29371 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29371 exists.
Other vulnerabilities in n/a
Sources
Also known as CLEANSTART-2026-AT07752, CLEANSTART-2026-AU34344, CLEANSTART-2026-GN63905, CLEANSTART-2026-WA75258, DEBIAN-CVE-2024-29371, ECHO-dd2d-0ee6-be04 and 14 more.