Loading vulnerability…
CVE-2013-1624 is a timing side-channel vulnerability in the TLS implementation of Bouncy Castle Java versions before 1.48 and Bouncy Castle C# versions before 1.8. When processing malformed CBC-mode TLS/SSL records, the noncompliant MAC-check path does not adequately eliminate timing differences associated with padding validation. An attacker can statistically distinguish these timing differences and use a vulnerable TLS/SSL endpoint as a padding oracle, similarly to the issue addressed by CVE-2013-0169.
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.
Bouncy Castle TLS CBC padding timing attack.
A TLS/SSL CBC-mode padding-oracle vulnerability in Bouncy Castle arising from timing information leakage during encrypted-record decryption.
A TLS/SSL CBC padding-oracle vulnerability in Bouncy Castle caused by timing information leakage during encrypted-record decryption.
A timing side-channel vulnerability in Bouncy Castle CBC-mode TLS/SSL record decryption that could facilitate padding-oracle recovery of encrypted 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.