CVE-2024-45039 json
gnark's Groth16 commitment extension unsound for more than one commitment
published 2024-09-06 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-2851 , GHSA-q3hw-3gm4-w5cr , GO-2024-3122
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
gnark is a fast zk-SNARK library that offers a high-level API to design circuits. Versions prior to 0.11.0 have a soundness issue - in case of multiple commitments used inside the circuit the prover is able to choose all but the last commitment. As gnark uses the commitments for optimized non-native multiplication, lookup checks etc. as random challenges, then it could impact the soundness of the whole circuit. However, using multiple commitments has been discouraged due to the additional cost to the verifier and it has not been supported in the recursive in-circuit Groth16 verifier and Solidity verifier. gnark's maintainers expect the impact of the issue be very small - only for the users who have implemented the native Groth16 verifier or are using it with multiple commitments. We do not have information of such users. The issue has been patched in version 0.11.0. As a workaround, users should follow gnark maintainers' recommendation to use only a single commitment and then derive in-circuit commitments as needed using the `std/multicommit` package.
Patch / fix
- go github.com/consensys/gnark 0.11.0
- Consensys gnark 0.11.0
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20241213T205935-1.1
opensuse advisories openSUSE-SU-2024:14599-1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/consensys/gnark | <0.11.0 |
0.11.0 |
Affected products
- Consensys gnark
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/Consensys/gnark/commit/e7c66b000454f4d2a4ae48c005c34154d4cfc2a2
web, broken-link
-
github.com
/Consensys/gnark/security/advisories/GHSA-q3hw-3gm4-w5cr
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-45039
advisory
-
github.com
/Consensys/gnark
package
-
pkg.go.dev
/vuln/GO-2024-3122
web
Sources
- CVE List CVE-2024-45039
- GitHub Advisory GHSA-q3hw-3gm4-w5cr
- NVD CVE-2024-45039
- OSV GO-2024-3122
Fencer Vulns 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.