8 matches found
EUVD-2025-8645
Malicious code in bioql PyPI...
SUSE CVE-2025-29072
An integer overflow in Nethermind Juno before v.12.05 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...
GO-2025-3583 Nethermind Juno Potential Denial of Service (DoS) via Integer Overflow in github.com/NethermindEth/juno
Nethermind Juno Potential Denial of Service DoS via Integer Overflow in github.com/NethermindEth/juno...
CVE-2025-29072
An integer overflow in Nethermind Juno before v.12.05 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...
CVE-2025-29072
An integer overflow in Nethermind Juno before v.12.05 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...
CVE-2025-29072
An integer overflow in Nethermind Juno before v.12.05 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...
CVE-2025-29072
An integer overflow in Nethermind Juno before v.12.05 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...
CVE-2025-29072
The CVE-2025-29072 entry describes an integer overflow in Nethermind Juno (pre-12.05) within the Sierra bytecode decompression logic of cairo-lang-starknet-classes that can be triggered by a malicious Declare v2/v3 transaction, causing a Denial of Service with high CPU usage on Starknet full-node...