vyper 0.4.2rc1: vulnerabilidades conocidas

No se pudieron comparar 16 registros. Los resultados están incompletos.

1. CVE-2025-47774

   Baja · CVSS 2.9EPSS 0,48%Sin corrección publicada

   Vyper's `slice()` may elide side-effects when output length is 0

   Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or `<address>.code`). The reason is that for these source locations, the check that `length >= 1` is skipped. The result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0. The impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(m

   vyperPython

   Publicación 15 de mayo de 2025Actualización 15 de mayo de 2025

   Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

2. CVE-2025-47285

   Baja · CVSS 2.9EPSS 0,46%Sin corrección publicada

   Vyper's `concat()` builtin may elide side-effects for zero-length arguments

   Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, `concat()` may skip evaluation of side effects when the length of an argument is zero. This is due to a fastpath in the implementation which skips evaluation of argument expressions when their length is zero. In practice, it would be very unusual in user code to construct zero-length bytestrings using an expression with side-effects, since zero-length bytestrings are typically constructed with the empty literal `b""`; the only way to construct an empty bytestring which has side effects would be with the ternary operator intro

   vyperPython

   Publicación 15 de mayo de 2025Actualización 15 de mayo de 2025

   Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

3. CVE-2025-21607

   Baja · CVSS 2.3EPSS 0,67%Sin corrección publicada

   Success of Certain Precompile Calls not Checked in Vyper

   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. No

   vyperPython

   Publicación 14 de enero de 2025Actualización 24 de abril de 2025

   Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

4. CVE-2023-40015

   Baja · CVSS 3.7EPSS 0,49%Sin corrección publicada

   Vyper: reversed order of side effects for some operations

   Vyper is a Pythonic Smart Contract Language. For the following (probably non-exhaustive) list of expressions, the compiler evaluates the arguments from right to left instead of left to right. `unsafe_add, unsafe_sub, unsafe_mul, unsafe_div, pow_mod256, |, &, ^ (bitwise operators), bitwise_or (deprecated), bitwise_and (deprecated), bitwise_xor (deprecated), raw_call, <, >, <=, >=, ==, !=, in, not in (when lhs and rhs are enums)`. This behaviour becomes a problem when the evaluation of one of the arguments produces side effects that other arguments depend on. The following expressions can produce side-effect: state modifying external call , sta

   vyperPython

   Publicación 4 de septiembre de 2023Actualización 19 de noviembre de 2024

   Aviso original 1 ↗Aviso original 2 ↗

5. CVE-2023-39363

   Crítica · CVSS 9.1EPSS 0,82%Sin corrección publicada

   Vyper incorrectly allocated named re-entrancy locks

   Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). In versions 0.2.15, 0.2.16 and 0.3.0, named re-entrancy locks are allocated incorrectly. Each function using a named re-entrancy lock gets a unique lock regardless of the key, allowing cross-function re-entrancy in contracts compiled with the susceptible versions. A specific set of conditions is required to result in misbehavior of affected contracts, specifically: a `.vy` contract compiled with `vyper` versions `0.2.15`, `0.2.16`, or `0.3.0`; a primary function that utilizes the `@nonreentrant` decorator with a specific `key` and does not strictly follow the

   vyperPython

   Publicación 7 de agosto de 2023Actualización 11 de octubre de 2024

   Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗