Loading vulnerability…
CVE-2023-51775 is an improper input-validation vulnerability in jose4j before version 0.9.4. Processing a JSON Web Encryption (JWE) object containing an excessively large PBES2 Count (p2c) value can cause excessive CPU consumption, resulting in denial of service.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A jose4j denial-of-service vulnerability triggered through a specially crafted JWE.
A denial-of-service vulnerability in jose4j triggered by a specially crafted JSON Web Encryption (JWE) object.
Denial-of-service vulnerability in jose4j triggered by a specially crafted JWE.
A jose4j denial-of-service vulnerability triggered through a specially crafted JWE.
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.