Skip to content

Commit 6380847

Browse files
1 parent 256c011 commit 6380847

2 files changed

Lines changed: 119 additions & 0 deletions

File tree

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-cp57-fq8g-qh6v",
4+
"modified": "2026-03-26T18:00:28Z",
5+
"published": "2026-03-26T18:00:28Z",
6+
"aliases": [],
7+
"summary": "libcrux has an Incorrect Check of Signer Response Norm During Verification",
8+
"details": "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.\n\nlibcrux-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.\n\n## Impact\nApplications using libcrux-ml-dsa for signature verification would have accepted signatures that would be rejected by a conforming implementation.\n\n## Mitigation\nStarting from version `0.0.8`, signature verification uses the correct value for $\\gamma_1$ in the signer response norm check.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "crates.io",
19+
"name": "libcrux-ml-dsa"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "0.0.8"
30+
}
31+
]
32+
}
33+
]
34+
}
35+
],
36+
"references": [
37+
{
38+
"type": "WEB",
39+
"url": "https://github.com/cryspen/libcrux/pull/1347"
40+
},
41+
{
42+
"type": "PACKAGE",
43+
"url": "https://github.com/cryspen/libcrux"
44+
},
45+
{
46+
"type": "WEB",
47+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0077.html"
48+
}
49+
],
50+
"database_specific": {
51+
"cwe_ids": [
52+
"CWE-347"
53+
],
54+
"severity": "HIGH",
55+
"github_reviewed": true,
56+
"github_reviewed_at": "2026-03-26T18:00:28Z",
57+
"nvd_published_at": null
58+
}
59+
}
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-pv9v-5j35-xwcr",
4+
"modified": "2026-03-26T18:00:05Z",
5+
"published": "2026-03-26T18:00:05Z",
6+
"aliases": [],
7+
"summary": "libcrux Panics During Standalone MAC Operations",
8+
"details": "An incorrect constant for the key length in libcrux-poly1305 caused the standalone MAC function `libcrux_poly1305::mac` to always panic with an out-of-bounds memory access.\n\n## Impact\nApplications wishing to use libcrux-poly1305 as a standalone MAC would experience panics. The use of libcrux-poly1305 in libcrux-chacha20poly1305 is unaffected.\n\n## Mitigation\nStarting from version `0.0.5`, the correct value is used for the key length constant.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "crates.io",
19+
"name": "libcrux-poly1305"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "0.0.5"
30+
}
31+
]
32+
}
33+
]
34+
}
35+
],
36+
"references": [
37+
{
38+
"type": "WEB",
39+
"url": "https://github.com/cryspen/libcrux/pull/1351"
40+
},
41+
{
42+
"type": "PACKAGE",
43+
"url": "https://github.com/cryspen/libcrux"
44+
},
45+
{
46+
"type": "WEB",
47+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0073.html"
48+
}
49+
],
50+
"database_specific": {
51+
"cwe_ids": [
52+
"CWE-125",
53+
"CWE-805"
54+
],
55+
"severity": "HIGH",
56+
"github_reviewed": true,
57+
"github_reviewed_at": "2026-03-26T18:00:05Z",
58+
"nvd_published_at": null
59+
}
60+
}

0 commit comments

Comments
 (0)