Loading vulnerability…
Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 contains an incomplete remediation for the Bleichenbacher XML Encryption attack previously addressed as CVE-2011-2487. When processing encrypted keys or encrypted message data, distinguishable exception behavior reveals decryption-failure information. This behavior acts as a padding/decryption oracle, allowing an attacker to iteratively submit crafted XML Encryption messages and infer properties of RSA-decrypted ciphertext.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability listed among CVEs addressed by this Red Hat JBoss Portal 6.2.0 advisory; no technical description is provided.
A flaw in Apache WSS4J's prior mitigation for Bleichenbacher's XML Encryption attack that can allow remote recovery of a symmetric key's plaintext.
An incomplete countermeasure in Apache WSS4J for the XML Encryption Bleichenbacher attack. The observable exception behavior enabled an attacker to determine whether an attack attempt failed, preserving exposure to symmetric-key plaintext recovery.
An Apache WSS4J flaw in the countermeasure for XML Encryption Bleichenbacher attacks that retained an oracle enabling recovery of symmetric-key plaintext.
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.