libcrux-ml-dsa
Affected
- introduced
0.0.0-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: GHSA-cp57-fq8g-qh6v
Incorrect Check of Signer Response Norm During Verification
The ML-DSA verification algorithm as specified in [FIPS 204,
subsection
6.3](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf#subsection.6.3)
requires verifiers to check that the infinity norm of the deserialized
signer response $z$ does not exceed $\gamma_1 - \beta$ (line 13 of
Algorithm 8).
The same check is required to be performed during signature generation.
libcrux-ml-dsa did not perform this check correctly during signature
verification, accepting signatures with signer response norm above the
allowed maximum value. The check is correctly performed during
signing.
Impact
Applications using libcrux-ml-dsa for signature verification would
have accepted signatures that would be rejected by a conforming
implementation.
Mitigation
Starting from version 0.0.8, signature verification uses the correct
value for $\gamma_1$ in the signer response norm check.
Not rated by the source.
0.0.0-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: RustSec Advisory Database · CC0-1.0