Security Resilience

CVE-2024-14041

Bouncycastle Bc-Java 1.73 – 1.78

Public PoC
Published
28 July 2026
Modified
02 October 2026
Patch / advisory
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber
EPSS Score 0.0046 40th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-14041 is a high-severity Observable Timing Discrepancy (CWE-208) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Discovery (T1083); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM (CRYSTALS-Kyber) routines divided secret-derived polynomial coefficients by the modulus q: Poly.toMsg, which decodes the decrypted message, and the ciphertext compression routines Poly.compressPoly and PolyVec.compressPolyVec. An attacker able to…

more

measure the timing of a large number of decapsulations performed with the same long-term private key can recover that key. These are the KyberSlash1 (Poly.toMsg) and KyberSlash2 (ciphertext compression) divisions. Compression performed during encapsulation operates on values that become the public ciphertext and is not affected.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts that can be used during targeting.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-12852Same product: Bouncycastle Bc-Java
CVE-2026-59652Same product: Bouncycastle Bc-Java
CVE-2026-17507Same product: Bouncycastle Bc-Java
CVE-2023-33201Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-59644Same product: Bouncycastle Bc-Java
CVE-2026-12803Same product: Bouncycastle Bc-Java
CVE-2026-12816Same product: Bouncycastle Bc-Java
CVE-2026-12860Same product: Bouncycastle Bc-Java
CVE-2026-59643Same product: Bouncycastle Bc-Java

Affected Assets

bouncycastle
bc-java
1.73 — 1.78

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's SOURCE reach (code review, static analysis) catches obvious non-constant-time comparisons and early-exit loops in security-sensitive code, and its RUNTIME reach (penetration testing) can surface some timing discrepancies under focused timing analysis, but many timing side channels are too subtle for standard code review, evade static-analysis pattern matching, and require specialised statistical timing measurement that ordinary pen testing does not perform — a nameable remainder that keeps the grade at `partial`.

blocks

A.8.5 items (c) and (d) directly address timing-based information disclosure during log-on — not indicating which part of the data is correct/incorrect, and validating log-on information only on completion of all input — which blocks the byte-by-byte password comparison and differential-error timing attacks documented in CWE-208's observed examples; however, the clause does not reach timing discrepancies in cryptographic operations (HMAC comparison, padding checks) or other authentication-related timing side channels beyond the log-on procedure itself.

finds

A.8.8's reach is DISCLOSURE — it finds CWE-208 only where a vendor has published a CVE for a timing discrepancy in software present in the asset inventory and a scanner flags it. Several CWE-208 instances do surface as CVEs (CVE-2019-10071, CVE-2014-0984, CVE-2003-0078, etc.), so the class commonly discloses, but most timing discrepancies in custom or unexamined code are never published, capping the grade at `partial` under the disclosure-reach ceiling.

References