
Cloud Vulnerability DB
A community-led vulnerabilities database
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.
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.
Starting from version 0.0.8, hint decoding will check the cumulative
hint counter of the last row as well.
Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."