LiveActive security incident?Get immediate response
CVE Record

CVE-2025-14813: GOSTCTR implementation unable to process more than 255 blocks correctly

: 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. This issue affects BC-JAVA: from 1.59 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.

CriticalCVSS 9.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical cryptographic correctness issue in Bouncy Castle BC-JAVA. Systems using affected bcprov versions for GOST CTR processing may produce incorrect cryptographic results after more than 255 blocks, creating confidentiality and integrity risk where that cipher path protects sensitive data.

Executive priority

Treat as urgent for systems using Bouncy Castle in cryptographic workflows, especially where GOST CTR protects regulated or sensitive data. Prioritize inventory and upgrades, but avoid assuming every bcprov user is exploitable without confirming use of the affected cipher path.

Technical view

CVE-2025-14813 affects BC-JAVA bcprov core modules, specifically G3413CTRBlockCipher. The CVE maps to CWE-327 and describes a GOSTCTR implementation that cannot correctly process more than 255 blocks. Affected ranges are 1.59 before 1.80.2, 1.81 before 1.81.1, and 1.82 before 1.84.

Likely exposure

Exposure is most likely in Java applications or products bundling vulnerable bcprov versions and using GOSTCTR/G3413CTRBlockCipher. Dependency presence alone may not prove runtime exposure; confirm whether the affected cipher is reachable in production cryptographic workflows.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. CVSS v4.0 rates it 9.3 with local attack vector, low complexity, no privileges, and no user interaction, but exploitation evidence is not established in the bundle.

Researcher notes

The strongest evidence is the CVE record, Bouncy Castle advisory, and linked patch commits. The bundle does not provide exploit proof, detailed attack preconditions beyond CVSS, or product-specific reachability analysis. Validate runtime cipher use before escalating beyond dependency-based exposure.

Mitigation direction

  • Upgrade BC-JAVA 1.59-1.80.1 deployments to 1.80.2 or later.
  • Upgrade BC-JAVA 1.81 deployments to 1.81.1 or later.
  • Upgrade BC-JAVA 1.82-1.83 deployments to 1.84 or later.
  • Apply relevant Red Hat security errata for vendor-packaged dependencies.
  • Check upstream vendor guidance for product-specific remediation instructions.

Validation and detection

  • Inventory direct and transitive bcprov dependencies across Java applications.
  • Confirm deployed BC-JAVA versions against the affected ranges.
  • Search code and configuration for GOSTCTR or G3413CTRBlockCipher usage.
  • Verify patched artifacts are loaded at runtime, not only declared in builds.
  • Review vendor advisories for Red Hat-packaged exposure and errata status.
Prepared
Confidence
high
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-327: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-14813 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/RE:M/U:Red

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
18Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/RE:M/U:Red——bcorg
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2025-14813Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/RE:M/U:Red

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPbouncycastle: BC-JAVA: GOSTCTR implementation unable to process more than 255 blocks correctly
other:Red Hat severity ratingcvssV3_1
  • 2026-04-15T10:01:27.769Z: Reported to Red Hat.
  • 2026-04-15T08:56:34.057Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Legion of the Bouncy Castle Inc.BC-JAVAbcprov, 1.59, 1.81, 1.82unaffected
Weakness

CWE details

CWE-327

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-327 · source CWE mapping

Use of a Broken or Risky Cryptographic Algorithm

Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs