CVE-2025-14813 high CVSS 7.5

Vulnerability in org.bouncycastle:bcprov-jdk14 (CVE-2025-14813)

Summary

Vulnerability in org.bouncycastle:bcprov-jdk14 (CVE-2025-14813). Confidential information can be exposed externally. Exploitable via G3413CTRBlockCipher. Mitigation: upgrade to 1.84 or later.

Original description

The description as published by the source.

The GOST 28147-2015 CTR mode implementation (G3413CTRBlockCipher) in the Legion of the Bouncy Castle BC-JAVA bcprov core module only increments the final byte of the counter, so the counter wraps after 255 blocks and the keystream is reused. Reusing CTR keystream allows an attacker who can observe two ciphertexts produced with the same key/IV to recover the XOR of the plaintexts, breaking confidentiality. Affects BC-JAVA from 1.59 before 1.84 (with backported fixes in 1.80.2 and 1.81.1).

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-14813 has been found in org.bouncycastle:bcprov-jdk14.
Attackers can target a specific entry point like G3413CTRBlockCipher over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade org.bouncycastle:bcprov-jdk14 to 1.84 or later.
If unsure, ask your IT team or search "org.bouncycastle:bcprov-jdk14 CVE-2025-14813" on the vendor's site.

CVE-2025-14813 (org.bouncycastle:bcprov-jdk14) — CWE-327 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: G3413CTRBlockCipher / bcprov
Patched: 1.84 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-327) exists in org.bouncycastle:bcprov-jdk14. Attackers reach the vulnerable code path via G3413CTRBlockCipher without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.bouncycastle:bcprov-jdk14. Attack surface: G3413CTRBlockCipher / bcprov.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.84.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで org.bouncycastle:bcprov-jdk14 を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade org.bouncycastle:bcprov-jdk14 to 1.84
```
ステージング環境で 1.84 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.bouncycastle:bcprov-jdk14

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-jdk15to18

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-jdk18on

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-debug-jdk14

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-debug-jdk15to18

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-debug-jdk18on

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84"}]}]

maven org.bouncycastle:bcprov-ext-jdk14