CVE-2025-14813 | Legion of the Bouncy Castle BC-JAVA up to 1.83 risky encryption

VDB-357692 · CVE-2025-14813 · GCVE-0-2025-14813 LEGION OF THE BOUNCY CASTLE BC-JAVA UP TO 1.83 RISKY ENCRYPTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 2.4 $0-$5k 2.97+ Summaryinfo A vulnerability was found in Legion of the Bouncy Castle BC-JAVA up to 1.83. It has been declared as problematic. Impacted is an unknown function. Such manipulation leads to risky encryption. This vulnerability is uniquely identified as CVE-2025-14813. Local access is required to approach this attack. No exploit exists. It is recommended to upgrade the affected component. Detailsinfo A vulnerability was found in Legion of the Bouncy Castle BC-JAVA up to 1.83 and classified as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a risky encryption vulnerability. Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality. CVE summarizes: Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (core modules). This vulnerability is associated with program files G3413CTRBlockCipher. GOSTCTR implementation unable to process more than 255 blocks correctly. This issue affects BC-JAVA: from 1.59 before 1.84. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-14813 since 12/17/2025. The exploitation is known to be difficult. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600. Upgrading to version 1.84 eliminates this vulnerability. Productinfo Type Programming Language Software Vendor Legion of the Bouncy Castle Name BC-JAVA Version 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 1.48 1.49 1.50 1.51 1.52 1.53 1.54 1.55 1.56 1.57 1.58 1.59 1.60 1.61 1.62 1.63 1.64 1.65 1.66 1.67 1.68 1.69 1.70 1.71 1.72 1.73 1.74 1.75 1.76 1.77 1.78 1.79 1.80 1.81 1.82 1.83 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 2.5 VulDB Meta Temp Score: 2.4 VulDB Base Score: 2.5 VulDB Temp Score: 2.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Risky encryption CWE: CWE-327 / CWE-310 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: BC-JAVA 1.84 Timelineinfo 12/17/2025 CVE reserved 04/15/2026 +118 days Advisory disclosed 04/15/2026 +0 days VulDB entry created 04/15/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Status: Confirmed CVE: CVE-2025-14813 (🔒) GCVE (CVE): GCVE-0-2025-14813 GCVE (VulDB): GCVE-100-357692 Entryinfo Created: 04/15/2026 11:48 Changes: 04/15/2026 11:48 (68) Complete: 🔍 Cache ID: 99:93A:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸