CVE-2023-31146 — Out-of-bounds Write in Vyperlang Vyper

Vendor	Product	Version range	Fixed in
vyperlang	vyper	< 0.3.8	0.3.8
vyperlang	vyper	>= 0 < 0.3.8	0.3.8
vyperlang	vyper	>= 0 < 4f8289a81206f767df1900ac48f485d90fc87edb	4f8289a81206f767df1900ac48f485d90fc87edb

GHSA

Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment

ghsa·2023-05-12

CVE-2023-31146 [HIGH] CWE-787 Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment ### Impact during codegen, the length word of a dynarray is written before the data, which can result in OOB array access in the case where the dynarray is on both the lhs and rhs of an assignment. here is a minimal example producing the issue: ```vyper a:DynArray[uint256,3] @external def test() -> DynArray[uint256,3]: self.a = [1,2,3] self.a = empty(DynArray[uint256,3]) self.a = [self.a[0],self.a[1],self.a[2]] return self.a # return [1,2,3] ``` and here is an example demonstrating the issue can cause data corruption across call frames: ```vyper @external def test() -> DynArray[uint256,3]: self.a() return self.b() # return [1,2,3] @internal def a(): a: uint256 = 0 b: uint256 = 1 c: uint256 = 2 d:

OSV

Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment

osv·2023-05-12

CVE-2023-31146 [HIGH] Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment Vyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignment ### Impact during codegen, the length word of a dynarray is written before the data, which can result in OOB array access in the case where the dynarray is on both the lhs and rhs of an assignment. here is a minimal example producing the issue: ```vyper a:DynArray[uint256,3] @external def test() -> DynArray[uint256,3]: self.a = [1,2,3] self.a = empty(DynArray[uint256,3]) self.a = [self.a[0],self.a[1],self.a[2]] return self.a # return [1,2,3] ``` and here is an example demonstrating the issue can cause data corruption across call frames: ```vyper @external def test() -> DynArray[uint256,3]: self.a() return self.b() # return [1,2,3] @internal def a(): a: uint256 = 0 b: uint256 = 1 c: uint256 = 2 d:

OSV

CVE-2023-31146: Vyper is a Pythonic smart contract language for the Ethereum virtual machine

osv·2023-05-11

CVE-2023-31146 CVE-2023-31146: Vyper is a Pythonic smart contract language for the Ethereum virtual machine 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.

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…

Affected