cve.bz

CVE-2024-50354 consensys gnark: Uncontrolled Resource Consumption

5.5 mediumExploit referenceEPSS 0.3%Fix available

Medium (5.5) in consensys gnark. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/consensys/gnark 0.11.1, 0.12.0.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2024-10-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-50354 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-50354?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-50354?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-50354 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
consensys:gnarkbefore 0.12.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cph5-3pgr-c82gGogithub.com/consensys/gnark<0.11.10.11.1
GO-2024-3244Gogithub.com/consensys/gnark<0.12.00.12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP5, Linux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20241104T154416-150000.1.12.1SUSE-SU-2024:3950-1
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250207T224745-150000.1.32.1SUSE-SU-2025:0429-1
SUSEPackage Hub 12govulncheck-vulndb0.0.20241104T154416-5.1openSUSE-SU-2024:0350-1
openSUSELeap 15.5, Leap 15.6govulncheck-vulndb0.0.20241104T154416-150000.1.12.1SUSE-SU-2024:3950-1
openSUSELeap 15.6govulncheck-vulndb0.0.20250207T224745-150000.1.32.1SUSE-SU-2025:0429-1
openSUSETumbleweedgovulncheck-vulndb0.0.20241101T215616-1.1openSUSE-SU-2024:14452-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON