Skip to content

Nethermind Juno Potential Denial of Service (DoS) via Integer Overflow

High severity GitHub Reviewed Published Mar 27, 2025 to the GitHub Advisory Database • Updated Mar 28, 2025

Package

gomod github.com/NethermindEth/juno (Go)

Affected versions

< 0.12.5

Patched versions

0.12.5

Description

An integer overflow in Nethermind Juno before v0.12.5 within the Sierra bytecode decompression logic within the "cairo-lang-starknet-classes" library could allow remote attackers to trigger an infinite loop (and high CPU usage) by submitting a malicious Declare v2/v3 transaction. This results in a denial-of-service condition for affected Starknet full-node implementations.

References

Published by the National Vulnerability Database Mar 27, 2025
Published to the GitHub Advisory Database Mar 27, 2025
Reviewed Mar 28, 2025
Last updated Mar 28, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(26th percentile)

Weaknesses

CVE ID

CVE-2025-29072

GHSA ID

GHSA-wq32-8rp4-w2mc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.