pysec-2025-33
Vulnerability from pysec
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.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "vyper",
"purl": "pkg:pypi/vyper"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.4.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0b1",
"0.1.0b10",
"0.1.0b11",
"0.1.0b12",
"0.1.0b13",
"0.1.0b14",
"0.1.0b15",
"0.1.0b16",
"0.1.0b17",
"0.1.0b2",
"0.1.0b3",
"0.1.0b4",
"0.1.0b5",
"0.1.0b6",
"0.1.0b7",
"0.1.0b8",
"0.1.0b9",
"0.2.1",
"0.2.10",
"0.2.11",
"0.2.12",
"0.2.13",
"0.2.14",
"0.2.15",
"0.2.16",
"0.2.2",
"0.2.3",
"0.2.4",
"0.2.5",
"0.2.6",
"0.2.7",
"0.2.8",
"0.2.9",
"0.3.0",
"0.3.1",
"0.3.10",
"0.3.10rc1",
"0.3.10rc2",
"0.3.10rc3",
"0.3.10rc4",
"0.3.10rc5",
"0.3.2",
"0.3.3",
"0.3.4",
"0.3.5",
"0.3.6",
"0.3.7",
"0.3.8",
"0.3.9",
"0.4.0",
"0.4.0b1",
"0.4.0b2",
"0.4.0b3",
"0.4.0b4",
"0.4.0b5",
"0.4.0b6",
"0.4.0rc1",
"0.4.0rc2",
"0.4.0rc3",
"0.4.0rc4",
"0.4.0rc5",
"0.4.0rc6",
"0.4.1b1",
"0.4.1b2",
"0.4.1b3",
"0.4.1b4",
"0.4.1rc1",
"0.4.1rc2",
"0.4.1rc3"
]
}
],
"aliases": [
"CVE-2025-21607"
],
"details": "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\u0027s 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.",
"id": "PYSEC-2025-33",
"modified": "2025-04-23T21:23:01.322686+00:00",
"published": "2025-01-14T18:16:05+00:00",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-vgf2-gvx8-xwc3"
},
{
"type": "EVIDENCE",
"url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-vgf2-gvx8-xwc3"
}
],
"related": [
"GHSA-vgf2-gvx8-xwc3",
"GHSA-vgf2-gvx8-xwc3"
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.