CVEvulnerability

CVE-2024-14041

8.2 HIGH Published 2026-07-28 Modified 2026-10-02 Official page ↗
Status
Analyzed
Published
2026-07-28
Last modified
2026-10-02
Assigner
91579145-5d7b-4cc5-b925-a0262ff19630
CVSS 4.0 (91579145-5d7b-4cc5-b925-a0262ff19630)
8.2 HIGH — CVSS: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
CVSS 3.1 ([email protected])
5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-208

Description

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 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.

Affected configurations

• bouncycastle bc-java (>= 1.73 < 1.78)

Related

Weakness · CWE (1)

  • CWE-208 Observable Timing Discrepancy weakness

References