Skip to content
Fencer Intel
high —

GHSA-2cgv-28vr-rv6j json

libcrux incorrectly calculates on aarch64

published 11mo ago modified 8mo ago also RUSTSEC-2025-0133

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

On platforms without the `core::arch::aarch64::vxarq_u64` intrinsic, an unverified fallback in `libcrux-intrinsics` v0.0.3 passed incorrect arguments and produced wrong results. This corrupted SHA-3 digests and caused `libcrux-ml-kem` and `libcrux-ml-dsa` to sample incorrectly, yielding incorrect shared secrets and invalid signatures.

The issue has been fixed in v0.0.4.

Patch / fix

  • crates.io libcrux-intrinsics 0.0.4
  • crates.io libcrux-ml-kem 0.0.4
  • crates.io libcrux-ml-dsa 0.0.4

Is GHSA-2cgv-28vr-rv6j in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io libcrux-intrinsics
>=0.0.3, <0.0.4
>=0.0.4-0, <0.0.4
0.0.4
crates.io libcrux-ml-kem
>=0.0.3, <0.0.4
0.0.4
crates.io libcrux-ml-dsa
>=0.0.3, <0.0.4
0.0.4

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.