CVE-2024-45039 gnark's Groth16 commitment extension unsound for more than one commitment
A soundness flaw in gnark allows provers to manipulate commitments in circuits using multiple commitments, potentially bypassing verification checks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-45039?
CVE-2024-45039 is a medium-severity vulnerability in Consensys gnark, published on 6 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2024-45039?
3 open source packages ship an affected version, including github.com/consensys/gnark. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/consensys/gnark Go | All versions | 0.11.0 |
github.com/consensys/gnark Go | All versions | 0.11.0 |
github.com/consensys/gnark Go | All versions | 0.11.0 |
Products include Consensys Gnark-Crypto.
How do I fix CVE-2024-45039?
Upgrade github.com/consensys/gnark to 0.11.0 or later.
Is CVE-2024-45039 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45039 exists.
Other vulnerabilities in Consensys gnark
Sources
Also known as GHSA-q3hw-3gm4-w5cr, GO-2024-3122.