Loading vulnerability…
CVE-2024-29371 affects jose4j before version 0.9.6. The library can be forced into excessive resource consumption when processing a crafted JSON Web Encryption (JWE) token that uses compressed content with an exceptionally high compression ratio. During JWE handling, decompression of attacker-controlled data can trigger disproportionate memory allocation and CPU time, resulting in a decompression-bomb style denial-of-service condition. The provided context identifies this issue in the org.bitbucket.b_c:jose4j dependency and notes exposure in downstream products such as Confluence Data Center via the bundled dependency.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.