/

CVE-2025-14813

Severity:

HIGH RISK

(7.5)

Weak GCM-like Cipher (CWE-327) in Bouncy Castle BC-JAVA

CVE-2025-14813

Awaiting Analysis

Vulnerability type

Category:

Use of Weak Cryptographic Algorithm

CWE:

CWE-327

Impact:

Confidentiality and Integrity Compromise

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A weak or risky cryptographic algorithm in Bouncy Castle's BC-JAVA core modules affects the G3413CTRBlockCipher implementation, leading to reduced confidentiality guarantees.

When applications rely on this cipher mode for protecting sensitive data, attackers may be able to undermine encryption strength and recover or manipulate protected information.

Affected context

The vulnerability manifests in applications that integrate Bouncy Castle BC-JAVA core modules and use the G3413CTRBlockCipher or related constructs as part of their encryption pipeline.

It is most relevant where the cipher is used for protecting long-term secrets (such as stored data, tokens, or keys) and where cryptographic strength is assumed to meet modern security expectations.

Systems that rely on BC-JAVA versions from 1.59 up to certain 1.8x releases without additional cryptographic hardening are more likely to be impacted.

Exploit preconditions

  • Attack surface: Cryptographic operations that utilize the affected G3413CTRBlockCipher from BC-JAVA.
  • Required access: Ability to observe ciphertexts, influence plaintexts (e.g., chosen-plaintext scenarios), or interact with encryption/decryption services that use the vulnerable cipher.
  • Trigger point: Execution of encryption or decryption operations using the risky algorithm implementation in the vulnerable library versions.
  • Why exploitation is possible: The cipher construction does not meet robust cryptographic properties, allowing an adversary to exploit structural weaknesses to reduce effective security, potentially aiding key or plaintext recovery.

Why this happens

The underlying issue is the reliance on a cryptographic algorithm or mode that does not provide the intended level of security under practical usage conditions.

This maps to CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the library offers or implements cipher functionality with known or emerging weaknesses that can be exploited.

In this case, the G3413CTRBlockCipher implementation in BC-JAVA may expose patterns or predictable relationships between plaintext and ciphertext, enabling attackers to weaken confidentiality or integrity protections when the cipher is used for sensitive data.

Potential impact

  • Confidential data protected by the vulnerable cipher may be recoverable under certain attack models.
  • Encrypted application traffic or stored records could be exposed to cryptanalysis, reducing overall security.
  • Integrity of encrypted messages or tokens may be compromised, allowing tampering without detection.
  • Security assumptions underpinning authentication, authorization, or session management may be weakened.

General mitigation guidance

Mitigation generally centers on avoiding risky cryptographic primitives and favoring well-reviewed, standard algorithms with strong security proofs and broad ecosystem support.

Recommended patterns include:

  • Migrating encryption workflows to modern, authenticated encryption modes (e.g., AES-GCM or AES-CCM) using robust key and nonce management.
  • Applying clear crypto-agility practices so systems can switch away from deprecated algorithms without major refactoring.
  • Limiting long-term reliance on a single cipher and periodically re-evaluating cryptographic choices against current best practices and standards.
  • Minimizing exposure of sensitive data by layering defenses (e.g., transport-level encryption plus application-level encryption and strict access controls).

How teams detect issues like this

Effective detection focuses on identifying use of deprecated or risky algorithms at design and implementation time:

  • Static analysis rules that flag references to non-recommended cipher classes or modes, including custom CTR-like constructions.
  • Code review checklists that require developers to justify cryptographic choices and reference current standards or guidance (e.g., NIST, IETF).
  • Dependency and SBOM analysis to surface libraries exposing risky primitives or outdated crypto defaults.
  • Organization-wide crypto policies that define approved cipher suites and disallow custom or obscure algorithms without security review.

Sources

SourceLink
github.comgithub.com/bcgit/bc-java/commit/701686cb0184cd9ae103c801b3581fdf95c6d4f3
github.comgithub.com/bcgit/bc-java/commit/b42574345414e4b7c8051b16fa1fafe01c29871f
github.comgithub.com/bcgit/bc-java/wiki/CVE%E2%80%902025%E2%80%9014813
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11720
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11721
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13631
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14272
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14276
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17668
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18054
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18055
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18059
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21772
access.redhat.comaccess.redhat.com/errata/RHSA-2026:24977
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53644
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53645
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53646
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60239
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60246
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60247
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60248
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60249
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60250
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60251
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60252
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60254
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60256
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60259
access.redhat.comaccess.redhat.com/errata/RHSA-2026:66488
access.redhat.comaccess.redhat.com/security/cve/CVE-2025-14813
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2458640
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-14813.json

Frequently asked

questions

Exploitability depends on how heavily the affected cipher is used to protect sensitive data and whether attackers can observe or influence encrypted traffic. Systems that use the algorithm for core confidentiality guarantees are more exposed.

Typically, an attacker must at least be able to access ciphertexts produced by the vulnerable algorithm, and in stronger attack scenarios, interact with encryption or decryption services (e.g., chosen-plaintext attacks).

The safest pattern is to remove reliance on the risky cipher entirely and adopt standard, well-reviewed authenticated encryption algorithms, combined with sound key management and nonces.

Establish a cryptography governance process: use only widely vetted algorithms, periodically review crypto choices, enforce automated detection of non-approved primitives, and ensure cryptographic design changes undergo security review.

Find out what's already
exploitable in your codebase.