vyperlang vyper up to 0.3.x control flow

Summaryinfo

A vulnerability categorized as problematic has been discovered in vyperlang vyper up to 0.3.x. This affects an unknown part. Such manipulation leads to control flow. This vulnerability is documented as CVE-2025-21607. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in vyperlang vyper up to 0.3.x. Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a control flow vulnerability. Using CWE to declare the problem leads to CWE-670. The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. Impacted is integrity. CVE summarizes:

Vyper is a Pythonic Smart Contract Language for the EVM. When the Vyper Compiler uses the precompiles EcRecover (0x1) and Identity (0x4), the success flag of the call is not checked. As a consequence an attacker can provide a specific amount of gas to make these calls fail but let the overall execution continue. Then the execution result can be incorrect. Based on EVM's rules, after the failed precompile the remaining code has only 1/64 of the pre-call-gas left (as 63/64 were forwarded and spent). Hence, only fairly simple executions can follow the failed precompile calls. Therefore, we found no significantly impacted real-world contracts. None the less an advisory has been made out of an abundance of caution. There are no actions for users to take.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-21607 since 12/29/2024. The exploitation is known to be difficult. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/14/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• vyperlang

Name

• vyper

Version

• 0.1
• 0.2
• 0.3

Website

• Product: https://github.com/vyperlang/vyper/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion