Loading vulnerability…
CVE-2025-14813 is a cryptographic implementation flaw in the BC-JAVA bcprov core module's GOST 28147-2015 CTR-mode implementation, G3413CTRBlockCipher. The implementation increments only the final counter byte, causing the counter to wrap after 255 blocks and reuse CTR keystream material when additional blocks are processed. Affected releases are BC-JAVA 1.59 through 1.80.1, 1.81.0, and 1.82 through 1.83; fixed releases include 1.80.2, 1.81.1, and 1.84.
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.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability tracked as CVE-2025-14813 affecting TencentOS Server 4, with the associated component indicated as Bouncy Castle.
A Bouncy Castle cryptographic implementation flaw in GOSTCTR that fails to process more than 255 blocks correctly.
A Bouncy Castle cryptographic implementation flaw where GOSTCTR cannot correctly process more than 255 blocks.
A flaw in Bouncy Castle's GOSTCTR implementation that cannot correctly process more than 255 blocks.
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.