libcrux-ml-dsa
Affected
- introduced
0, fixed0.0.8(semver)
Fixed versions
0.0.8
Fix
- Fixed version
0.0.8cargo update -p libcrux-ml-dsa --precise 0.0.8
Advisory
Also known as: RUSTSEC-2026-0076
libcrux: Panic in Signature Hint Decoding During Verification
During ML-DSA verification the serialized hint values are decoded as specified in algorithm 22 HintBitUnpack of FIPS 204, subsection 7.1. The algorithm requires that the cumulative hint counters per row of the hint vector are strictly increasing and below a maximum value which depends on the choice of ML-DSA parameter set (line 4).
In libcrux-ml-dsa, hint decoding did not check the boundedness of the cumulative hint counter of the last row of the hint vector.
Impact
A manipulated invalid hint can cause an out-of-bounds memory access since the hint decoding logic may attempt to read outside the bounds of the serialized signature, causing a runtime panic.
Mitigation
Starting from version 0.0.8, hint decoding will check the cumulative hint counter of the last row as well.
High Basis: The source's own band: HIGH
0, fixed 0.0.8 (semver)0.0.8
0.0.8cargo update -p libcrux-ml-dsa --precise 0.0.8Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0