Prover or verifier crash via unbounded key allocation
Published Oct 31, 2024 · Updated Oct 31, 2024
Uncontrolled resource consumption in Consensys gnark 0.11.0 and earlier allows local users to crash a prover or verifier. ReadFrom trusts the serialized Groth16 header's nbCommitments value and uses it as a slice length before validating the available commitment keys. Local users with low privileges need only supply a malicious proving or verification key, causing out-of-memory termination without data disclosure or modification.
Summary
What happened
Uncontrolled resource consumption in Consensys gnark 0.11.0 and earlier allows local users to crash a prover or verifier. ReadFrom trusts the serialized Groth16 header's nbCommitments value and uses it as a slice length before validating the available commitment keys. Local users with low privileges need only supply a malicious proving or verification key, causing out-of-memory termination without data disclosure or modification.
The record
- CVE
- CVE-2024-50354
- Published
- Oct 31, 2024
- Updated
- Oct 31, 2024
- Vendor
- Consensys
- Product
- gnark
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 31, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.11.0
- Affected versionversion=<= 0.11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- gnark Groth16 crafted-key proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo