CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 0CVE-2024-50354 – Out-of-memory during deserialization with crafted inputs
https://notcve.org/view.php?id=CVE-2024-50354
gnark is a fast zk-SNARK library that offers a high-level API to design circuits. In gnark 0.11.0 and earlier, deserialization of Groth16 verification keys allocate excessive memory, consuming a lot of resources and triggering a crash with the error fatal error: runtime: out of memory. • https://github.com/Consensys/gnark/commit/47ae846339add2bdf9983e499342bfdfe195191d https://github.com/Consensys/gnark/pull/1307 https://github.com/Consensys/gnark/security/advisories/GHSA-cph5-3pgr-c82g • CWE-400: Uncontrolled Resource Consumption •
CVSS: 6.2EPSS: 0%CPEs: 1EXPL: 0CVE-2024-45039 – gnark's Groth16 commitment extension unsound for more than one commitment
https://notcve.org/view.php?id=CVE-2024-45039
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. • https://github.com/Consensys/gnark/commit/e7c66b000454f4d2a4ae48c005c34154d4cfc2a2 https://github.com/Consensys/gnark/security/advisories/GHSA-q3hw-3gm4-w5cr • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 0CVE-2024-45040 – gnark's commitments to private witnesses in Groth16 as implemented break zero-knowledge property
https://notcve.org/view.php?id=CVE-2024-45040
gnark is a fast zk-SNARK library that offers a high-level API to design circuits. Prior to version 0.11.0, commitments to private witnesses in Groth16 as implemented break the zero-knowledge property. The vulnerability affects only Groth16 proofs with commitments. Notably, PLONK proofs are not affected. The vulnerability affects the zero-knowledge property of the proofs - in case the witness (secret or internal) values are small, then the attacker may be able to enumerate all possible choices to deduce the actual value. • https://github.com/Consensys/gnark/commit/afda68a38acca37becb8ba6d8982d03fee9559a0 https://github.com/Consensys/gnark/pull/1245 https://github.com/Consensys/gnark/security/advisories/GHSA-9xcg-3q8v-7fq6 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 0CVE-2023-44378 – gnark vulnerable to unsoundness in variable comparison/non-unique binary decomposition
https://notcve.org/view.php?id=CVE-2023-44378
gnark is a zk-SNARK library that offers a high-level API to design circuits. Prior to version 0.9.0, for some in-circuit values, it is possible to construct two valid decomposition to bits. In addition to the canonical decomposition of `a`, for small values there exists a second decomposition for `a+r` (where `r` is the modulus the values are being reduced by). The second decomposition was possible due to overflowing the field where the values are defined. Upgrading to version 0.9.0 should fix the issue without needing to change the calls to value comparison methods. gnark es una librería zk-SNARK que ofrece una API de alto nivel para diseñar circuitos. • https://github.com/Consensys/gnark/commit/59a4087261a6c73f13e80d695c17b398c3d0934f https://github.com/Consensys/gnark/security/advisories/GHSA-498w-5j49-vqjg https://github.com/zkopru-network/zkopru/issues/116 • CWE-191: Integer Underflow (Wrap or Wraparound) CWE-697: Incorrect Comparison •