Version 0.3.9

vyper

Pythonic Smart Contract Language for the EVM

Install Instructions

pip install vyper
Current Version Release Date June 20, 2024
Language Python
Package URL (purl) pkg:pip/vyper@0.3.9

Find vyper vulnerabilities in your supply chain.

Scan for Free

vyper Vulnerabilities

Sort by
icon CVE (Latest)
  • icon CVE (Latest)
  • icon CVE (Oldest)
  • icon CVSS Score (Highest)
  • icon CVSS Score (Lowest)
CVE question mark icon CVSS Score question mark icon CWE(s) question mark icon EPSS Score question mark icon EPSS % question mark icon Impacted Versions
CVE-2022-29255 High 7.5 CWE-670 0.00062 0.2782
  • 0.1.0b1–0.3.3
CVE-2023-30629 High 7.5 CWE-670 0.00132 0.49519
  • 0.3.1–0.3.7
CVE-2023-30837 High 7.5 CWE-789 0.00074 0.33467
  • 0.1.0b1–0.3.7
CVE-2023-31146 High 9.1 CWE-787 0.00118 0.47083
  • 0.1.0b1–0.3.7
CVE-2023-32058 High 7.5 CWE-190 0.00116 0.46666
  • 0.1.0b1–0.3.7
CVE-2023-32059 High 7.5 CWE-683 0.00079 0.35711
  • 0.1.0b1–0.3.7
CVE-2023-32675 Medium 5.3 CWE-670 0.00072 0.32963
  • 0.1.0b1–0.3.7
CVE-2023-37902 Medium 5.3 CWE-252 0.00075 0.34036
  • 0.1.0b1–0.3.10rc5
CVE-2023-40015 Medium 5.3 CWE-670 0.00067 0.31098
  • 0.1.0b1–0.4.1b1
CVE-2023-41052 Medium 5.3 CWE-670 0.00075 0.34036
  • 0.1.0b1–0.3.10rc5
CVE-2023-42441 Medium 5.3 CWE-833, CWE-667 0.00088 0.38916
  • 0.2.9–0.3.10rc5
CVE-2023-46247 High 7.5 CWE-193, CWE-682 0.0008 0.35831
  • 0.1.0b1–0.3.7
CVE-2024-22419 High 9.8 CWE-787, CWE-120 0.00099 0.42462
  • 0.3.0–0.3.10rc5
CVE-2024-24559 Medium 5.3 CWE-327, CWE-1284 0.00046 0.18477
  • 0.1.0b1–0.4.0b6
CVE-2024-24560 Medium 5.3 CWE-119 0.00046 0.18477
  • 0.1.0b1–0.4.0b6
CVE-2024-24561 High 9.8 CWE-119, CWE-787 0.00067 0.31194
  • 0.1.0b1–0.4.0b6
CVE-2024-24563 High 9.8 CWE-129 0.00068 0.31508
  • 0.1.0b1–0.4.0b6
CVE-2024-24564 Low 3.7 CWE-125 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2024-24567 Medium 5.3 CWE-754 0.00046 0.18477
  • 0.1.0b1–0.4.0b6
CVE-2024-26149 Low 3.7 CWE-119, CWE-120 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2024-32645 Medium 5.3 CWE-20 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2024-32646 Medium 5.3 CWE-20 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2024-32647 Medium 5.3 CWE-95 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2024-32649 Medium 5.3 CWE-95 0.00043 0.10302
  • 0.1.0b1–0.4.0b6
CVE-2023-42443 High 8.1 CWE-787 0.00145 0.51676
  • 0.3.4–0.3.10rc5
CVE-2023-42460 High 7.5 CWE-682 0.00077 0.34482
  • 0.3.4–0.3.10rc5
CVE-2021-41121 High 8.8 CWE-119 0.00104 0.43979
  • 0.1.0b1–0.2.16
CVE-2021-41122 Medium 4.3 CWE-682 0.00053 0.22719
  • 0.1.0b1–0.2.16
CVE-2022-24787 High 7.5 CWE-697 0.00062 0.28243
  • 0.1.0b1–0.3.1
CVE-2022-24788 High 9.8 CWE-119, CWE-120 0.00154 0.52753
  • 0.1.0b1–0.3.1
CVE-2022-24845 High 9.8 CWE-190 0.00236 0.62335
  • 0.1.0b1–0.3.1
CVE-2024-32648 Medium 5.3 CWE-667 0.00045 0.17069
  • 0.1.0b1–0.2.16
CVE-2023-39363 Medium 5.9 CWE-863 0.00117 0.46922
  • 0.2.15–0.3.0
CVE-2024-32481 Medium 5.3 CWE-681 0.00045 0.17069
  • 0.3.8–0.4.0b6

vyper Vulnerability Remediation Guidance

CVE Description Full list of Impacted Versions Fix
CVE-2024-32649 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, using the `sqrt` builtin can result in double eval vulnerability when the argument has side-effects. It can be seen that the `build_IR` function of the `sqrt` builtin doesn't cache the argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low. As of time of publication, no fixed versions are available. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-32648 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Prior to version 0.3.0, default functions don't respect nonreentrancy keys and the lock isn't emitted. No vulnerable production contracts were found. Additionally, using a lock on a `default` function is a very sparsely used pattern. As such, the impact is low. Version 0.3.0 contains a patch for the issue. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-32647 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, using the `create_from_blueprint` builtin can result in a double eval vulnerability when `raw_args=True` and the `args` argument has side-effects. It can be seen that the `_build_create_IR` function of the `create_from_blueprint` builtin doesn't cache the mentioned `args` argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low. As of time of publication, no fixed versions exist. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-32646 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, using the `slice` builtin can result in a double eval vulnerability when the buffer argument is either `msg.data`, `self.code` or `<address>.code` and either the `start` or `length` arguments have side-effects. It can be easily triggered only with the versions `<0.3.4` as `0.3.4` introduced the unique symbol fence. No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low. As of time of publication, no fixed versions are available. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-32645 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, incorrect values can be logged when `raw_log` builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in production. The `build_IR` function of the `RawLog` class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics. As of time of publication, no fixed version is available. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-32481 Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Starting in version 0.3.8 and prior to version 0.4.0b1, when looping over a `range` of the form `range(start, start + N)`, if `start` is negative, the execution will always revert. This issue is caused by an incorrect assertion inserted by the code generation of the range `stmt.parse_For_range()`. The issue arises when `start` is signed, instead of using `sle`, `le` is used and `start` is interpreted as an unsigned integer for the comparison. If it is a negative number, its 255th bit is set to `1` and is hence interpreted as a very large unsigned integer making the assertion always fail. Any contract having a `range(start, start + N)` where `start` is a signed integer with the possibility for `start` to be negative is affected. If a call goes through the loop while supplying a negative `start` the execution will revert. Version 0.4.0b1 fixes the issue. 0.4.0rc6, 0.4.0rc5, 0.4.0rc3, 0.4.0rc4, 0.4.0rc2, 0.4.0b5, 0.4.0b6, 0.4.0rc1 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-26149 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. If an excessively large value is specified as the starting index for an array in `_abi_decode`, it can cause the read position to overflow. This results in the decoding of values outside the intended array bounds, potentially leading to exploitations in contracts that use arrays within `_abi_decode`. This vulnerability affects 0.3.10 and earlier versions. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24567 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Vyper compiler allows passing a value in builtin raw_call even if the call is a delegatecall or a staticcall. But in the context of delegatecall and staticcall the handling of value is not possible due to the semantics of the respective opcodes, and vyper will silently ignore the value= argument. If the semantics of the EVM are unknown to the developer, he could suspect that by specifying the `value` kwarg, exactly the given amount will be sent along to the target. This vulnerability affects 0.3.10 and earlier versions. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24564 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. When using the built-in `extract32(b, start)`, if the `start` index provided has for side effect to update `b`, the byte array to extract `32` bytes from, it could be that some dirty memory is read and returned by `extract32`. This vulnerability is fixed in 0.4.0. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24563 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. Arrays can be keyed by a signed integer, while they are defined for unsigned integers only. The typechecker doesn't throw when spotting the usage of an `int` as an index for an array. The typechecker allows the usage of signed integers to be used as indexes to arrays. The vulnerability is present in different forms in all versions, including `0.3.10`. For ints, the 2's complement representation is used. Because the array was declared very large, the bounds checking will pass Negative values will simply be represented as very large numbers. As of time of publication, a fixed version does not exist. There are three potential vulnerability classes: unpredictable behavior, accessing inaccessible elements and denial of service. Class 1: If it is possible to index an array with a negative integer without reverting, this is most likely not anticipated by the developer and such accesses can cause unpredictable behavior for the contract. Class 2: If a contract has an invariant in the form `assert index < x`, the developer will suppose that no elements on indexes `y | y >= x` are accessible. However, by using negative indexes, this can be bypassed. Class 3: If the index is dependent on the state of the contract, this poses a risk of denial of service. If the state of the contract can be manipulated in such way that the index will be forced to be negative, the array access can always revert (because most likely the array won't be declared extremely large). However, all these the scenarios are highly unlikely. Most likely behavior is a revert on the bounds check. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24561 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice() function uses a non-literal argument for the start or length variable, this creates the ability for an attacker to overflow the bounds check. This issue can be used to do OOB access to storage, memory or calldata addresses. It can also be used to corrupt the length slot of the respective array. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24560 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. When calls to external contracts are made, we write the input buffer starting at byte 28, and allocate the return buffer to start at byte 0 (overlapping with the input buffer). When checking RETURNDATASIZE for dynamic types, the size is compared only to the minimum allowed size for that type, and not to the returned value's length. As a result, malformed return data can cause the contract to mistake data from the input buffer for returndata. When the called contract returns invalid ABIv2 encoded data, the calling contract can read different invalid data (from the dirty buffer) than the called contract returned. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-24559 Vyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2024-22419 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. The `concat` built-in can write over the bounds of the memory buffer that was allocated for it and thus overwrite existing valid data. The root cause is that the `build_IR` for `concat` doesn't properly adhere to the API of copy functions (for `>=0.3.2` the `copy_bytes` function). A contract search was performed and no vulnerable contracts were found in production. The buffer overflow can result in the change of semantics of the contract. The overflow is length-dependent and thus it might go unnoticed during contract testing. However, certainly not all usages of concat will result in overwritten valid data as we require it to be in an internal function and close to the return statement where other memory allocations don't occur. This issue has been addressed in 0.4.0. 0.3.2, 0.3.6, 0.3.0, 0.3.7, 0.3.5, 0.3.4, 0.3.1, 0.3.3 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-46247 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). Contracts containing large arrays might underallocate the number of slots they need by 1. Prior to v0.3.8, the calculation to determine how many slots a storage variable needed used `math.ceil(type_.size_in_bytes / 32)`. The intermediate floating point step can produce a rounding error if there are enough bits set in the IEEE-754 mantissa. Roughly speaking, if `type_.size_in_bytes` is large (> 2**46), and slightly less than a power of 2, the calculation can overestimate how many slots are needed by 1. If `type_.size_in_bytes` is slightly more than a power of 2, the calculation can underestimate how many slots are needed by 1. This issue is patched in version 0.3.8. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-42460 Vyper is a Pythonic Smart Contract Language for the EVM. The `_abi_decode()` function does not validate input when it is nested in an expression. Uses of `_abi_decode()` can be constructed which allow for bounds checking to be bypassed resulting in incorrect results. This issue has not yet been fixed, but a fix is expected in release `0.3.10`. Users are advised to reference pull request #3626. 0.3.6, 0.3.7, 0.3.5, 0.3.4, 0.3.10rc5, 0.3.10rc3, 0.3.10rc4, 0.3.10rc2 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-42443 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). In version 0.3.9 and prior, under certain conditions, the memory used by the builtins `raw_call`, `create_from_blueprint` and `create_copy_of` can be corrupted. For `raw_call`, the argument buffer of the call can be corrupted, leading to incorrect `calldata` in the sub-context. For `create_from_blueprint` and `create_copy_of`, the buffer for the to-be-deployed bytecode can be corrupted, leading to deploying incorrect bytecode. Each builtin has conditions that must be fulfilled for the corruption to happen. For `raw_call`, the `data` argument of the builtin must be `msg.data` and the `value` or `gas` passed to the builtin must be some complex expression that results in writing to the memory. For `create_copy_of`, the `value` or `salt` passed to the builtin must be some complex expression that results in writing to the memory. For `create_from_blueprint`, either no constructor parameters should be passed to the builtin or `raw_args` should be set to True, and the `value` or `salt` passed to the builtin must be some complex expression that results in writing to the memory. As of time of publication, no patched version exists. The issue is still being investigated, and there might be other cases where the corruption might happen. When the builtin is being called from an `internal` function `F`, the issue is not present provided that the function calling `F` wrote to memory before calling `F`. As a workaround, the complex expressions that are being passed as kwargs to the builtin should be cached in memory prior to the call to the builtin. 0.3.6, 0.3.7, 0.3.5, 0.3.4, 0.3.10rc5, 0.3.10rc3, 0.3.10rc4, 0.3.10rc2 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-42441 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). Starting in version 0.2.9 and prior to version 0.3.10, locks of the type `@nonreentrant("")` or `@nonreentrant('')` do not produce reentrancy checks at runtime. This issue is fixed in version 0.3.10. As a workaround, ensure the lock name is a non-empty string. 0.3.2, 0.3.6, 0.2.10, 0.3.0, 0.3.7, 0.3.5, 0.2.13, 0.2.14 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-41052 Vyper is a Pythonic Smart Contract Language. In affected versions the order of evaluation of the arguments of the builtin functions `uint256_addmod`, `uint256_mulmod`, `ecadd` and `ecmul` does not follow source order. This behaviour is problematic when the evaluation of one of the arguments produces side effects that other arguments depend on. A patch is currently being developed on pull request #3583. When using builtins from the list above, users should make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-40015 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 , state modifying internal call, `raw_call`, `pop()` when used on a Dynamic Array stored in the storage, `create_minimal_proxy_to`, `create_copy_of`, `create_from_blueprint`. This issue has not yet been patched. Users are advised to make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-39363 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 check-effects-interaction pattern (i.e. contains an external call to an untrusted party before storage updates); and a secondary function that utilizes the same `key` and would be affected by the improper state caused by the primary function. Version 0.3.1 contains a fix for this issue. 0.3.0, 0.2.16, 0.2.15 Patch → NO_SAFE_VERSION
CVE-2023-37902 Vyper is a Pythonic programming language that targets the Ethereum Virtual Machine (EVM). Prior to version 0.3.10, the ecrecover precompile does not fill the output buffer if the signature does not verify. However, the ecrecover builtin will still return whatever is at memory location 0. This means that the if the compiler has been convinced to write to the 0 memory location with specially crafted data (generally, this can happen with a hashmap access or immutable read) just before the ecrecover, a signature check might pass on an invalid signature. Version 0.3.10 contains a patch for this issue. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-32675 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In contracts with more than one regular nonpayable function, it is possible to send funds to the default function, even if the default function is marked `nonpayable`. This applies to contracts compiled with vyper versions prior to 0.3.8. This issue was fixed by the removal of the global `calldatasize` check in commit `02339dfda`. Users are advised to upgrade to version 0.3.8. Users unable to upgrade should avoid use of nonpayable default functions. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-32059 Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, internal calls with default arguments are compiled incorrectly. Depending on the number of arguments provided in the call, the defaults are added not right-to-left, but left-to-right. If the types are incompatible, typechecking is bypassed. The ability to pass kwargs to internal functions is an undocumented feature that is not well known about. The issue is patched in version 0.3.8. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-32058 Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, due to missing overflow check for loop variables, by assigning the iterator of a loop to a variable, it is possible to overflow the type of the latter. The issue seems to happen only in loops of type `for i in range(a, a + N)` as in loops of type `for i in range(start, stop)` and `for i in range(stop)`, the compiler is able to raise a `TypeMismatch` when trying to overflow the variable. The problem has been patched in version 0.3.8. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-31146 Vyper is a Pythonic smart contract language for the Ethereum virtual machine. Prior to version 0.3.8, during codegen, the length word of a dynarray is written before the data, which can result in out-of-bounds array access in the case where the dynarray is on both the lhs and rhs of an assignment. The issue can cause data corruption across call frames. The expected behavior is to revert due to out-of-bounds array access. Version 0.3.8 contains a patch for this issue. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-30837 Vyper is a pythonic smart contract language for the EVM. The storage allocator does not guard against allocation overflows in versions prior to 0.3.8. An attacker can overwrite the owner variable. This issue was fixed in version 0.3.8. 0.3.2, 0.3.6, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6 (Show all) Patch → NO_SAFE_VERSION
CVE-2023-30629 Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the `raw_call` with `revert_on_failure=False` and `max_outsize=0` receives the wrong response from `raw_call`. Depending on the memory garbage, the result can be either `True` or `False`. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put `max_outsize>0`. 0.3.2, 0.3.6, 0.3.7, 0.3.5, 0.3.4, 0.3.1, 0.3.3 Patch → NO_SAFE_VERSION
CVE-2022-29255 Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions prior to 0.3.4 when a calling an external contract with no return value, the contract address (including side effects) could be evaluated twice. This may result in incorrect outcomes for contracts. This issue has been addressed in v0.3.4. 0.3.2, 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7 (Show all) Patch → NO_SAFE_VERSION
CVE-2022-24845 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In affected versions, the return of `<iface>.returns_int128()` is not validated to fall within the bounds of `int128`. This issue can result in a misinterpretation of the integer value and lead to incorrect behavior. As of v0.3.0, `<iface>.returns_int128()` is validated in simple expressions, but not complex expressions. Users are advised to upgrade. There is no known workaround for this issue. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION
CVE-2022-24788 Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Versions of vyper prior to 0.3.2 suffer from a potential buffer overrun. Importing a function from a JSON interface which returns `bytes` generates bytecode which does not clamp bytes length, potentially resulting in a buffer overrun. Users are advised to upgrade. There are no known workarounds for this issue. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION
CVE-2022-24787 Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with `"\x00"` because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION
CVE-2021-41122 Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions external functions did not properly validate the bounds of decimal arguments. The can lead to logic errors. This issue has been resolved in version 0.3.0. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION
CVE-2021-41121 Vyper is a Pythonic Smart Contract Language for the EVM. In affected versions when performing a function call inside a literal struct, there is a memory corruption issue that occurs because of an incorrect pointer to the the top of the stack. This issue has been resolved in version 0.3.0. 0.2.1, 0.1.0b9, 0.1.0b8, 0.1.0b3, 0.1.0b4, 0.1.0b6, 0.1.0b7, 0.1.0b5 (Show all) Patch → NO_SAFE_VERSION

Instantly see if these vyper vulnerabilities affect your code.

Scan for Free

Dependencies

Packages using versions of vyper affected by its vulnerabilities

Dependent Packages
cbor2<6,>=5.4.6
asttokens<3,>=2.0.5
pycryptodome<4,>=3.5.1
packaging<24,>=23.1
importlib-metadata
wheel
ipython; extra == "dev"
pre-commit; extra == "dev"
pyinstaller; extra == "dev"
twine; extra == "dev"
pytest<9.0,>=8.0; extra == "dev"
pytest-cov<5.0,>=4.1; extra == "dev"
pytest-instafail<1.0,>=0.4; extra == "dev"
pytest-xdist<3.4,>=3.0; extra == "dev"
pytest-split<1.0,>=0.7.0; extra == "dev"
eth-abi<6.0.0,>=5.0.0; extra == "dev"
py-evm<0.11,>=0.10.1b1; extra == "dev"
lark==1.1.9; extra == "dev"
hypothesis[lark]<7.0,>=6.0; extra == "dev"
eth-stdlib==0.2.7; extra == "dev"
eth-account==0.12.2; extra == "dev"
setuptools; extra == "dev"
hexbytes>=1.2; extra == "dev"
pyrevm>=0.3.2; extra == "dev"
black==23.12.0; extra == "dev"
flake8==6.1.0; extra == "dev"
flake8-bugbear==23.12.2; extra == "dev"
flake8-use-fstring==1.4; extra == "dev"
isort==5.13.2; extra == "dev"
mypy==1.5; extra == "dev"
black==23.12.0; extra == "lint"
flake8==6.1.0; extra == "lint"
flake8-bugbear==23.12.2; extra == "lint"
flake8-use-fstring==1.4; extra == "lint"
isort==5.13.2; extra == "lint"
mypy==1.5; extra == "lint"
pytest<9.0,>=8.0; extra == "test"
pytest-cov<5.0,>=4.1; extra == "test"
pytest-instafail<1.0,>=0.4; extra == "test"
pytest-xdist<3.4,>=3.0; extra == "test"
pytest-split<1.0,>=0.7.0; extra == "test"
eth-abi<6.0.0,>=5.0.0; extra == "test"
py-evm<0.11,>=0.10.1b1; extra == "test"
lark==1.1.9; extra == "test"
hypothesis[lark]<7.0,>=6.0; extra == "test"
eth-stdlib==0.2.7; extra == "test"
eth-account==0.12.2; extra == "test"
setuptools; extra == "test"
hexbytes>=1.2; extra == "test"
pyrevm>=0.3.2; extra == "test"