Lucene search
+L

1014 matches found

Mend
Mend
•added 2026/10/21 12:36 a.m.•7 views

CVE-2020-37287

Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts passing multi-dimensional arrays or structs to internal or external functions receive corrupted values because the...

8.2CVSS6.1AI score0.00251EPSS
SaveExploits0References2
EUVD
EUVD
•added 2026/10/21 12:36 a.m.•7 views

EUVD-2020-31283

Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts passing multi-dimensional arrays or structs to internal or external functions receive corrupted values because the...

8.2CVSS6.1AI score0.00251EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/21 12:36 a.m.•18 views

CVE-2020-37288 Vyper 0.1.0b10 before 0.2.3 Invalid Jump Destination via Return in Nested Loops

Vyper from 0.1.0b10 before 0.2.3 generates incorrect code for a return statement inside a for loop in an internal function called two or more internal calls deep, producing an invalid jump destination stack underflow. Affected contracts revert such calls unnecessarily, which in limited...

6.3CVSS0.00284EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/21 12:36 a.m.•20 views

CVE-2020-37287 Vyper before 0.2.6 Call Stack Corruption via Complex Type Function Arguments

Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts passing multi-dimensional arrays or structs to internal or external functions receive corrupted values because the...

8.2CVSS0.00251EPSS
SaveExploits0References2
Mend
Mend
•added 2026/10/21 12:36 a.m.•4 views

CVE-2020-37288

Vyper from 0.1.0b10 before 0.2.3 generates incorrect code for a return statement inside a for loop in an internal function called two or more internal calls deep, producing an invalid jump destination stack underflow. Affected contracts revert such calls unnecessarily, which in limited...

6.3CVSS5.8AI score0.00284EPSS
SaveExploits0References2
Vulnrichment
Vulnrichment
•added 2026/10/21 12:36 a.m.•2 views

CVE-2020-37288 Vyper 0.1.0b10 before 0.2.3 Invalid Jump Destination via Return in Nested Loops

Vyper from 0.1.0b10 before 0.2.3 generates incorrect code for a return statement inside a for loop in an internal function called two or more internal calls deep, producing an invalid jump destination stack underflow. Affected contracts revert such calls unnecessarily, which in limited...

6.3CVSS5.8AI score0.00284EPSS
SaveExploits0References2
CVE
CVE
•added 2026/10/21 12:36 a.m.•8 views

CVE-2020-37288

Vyper versions 0.1.0b10 before 0.2.3 are vulnerable to an invalid jump destination caused by a stack underflow . This occurs when a return statement is used inside a for loop within an internal function that is called two or more internal calls deep. The compiler generates incorrect code for thes...

6.3CVSS5.8AI score0.00284EPSS
SaveExploits0References2
CVE
CVE
•added 2026/10/21 12:36 a.m.•10 views

CVE-2020-37287

Vyper versions prior to 0.2.6 are susceptible to a call stack corruption vulnerability. The root cause is an incorrect assumption by the compiler that each subtype size is 32, which occurs when complex types with non-base members are passed as function arguments. This flaw leads to corrupted func...

8.2CVSS6.1AI score0.00251EPSS
SaveExploits0References2
EUVD
EUVD
•added 2026/10/21 12:36 a.m.•5 views

EUVD-2020-31284

Vyper from 0.1.0b10 before 0.2.3 generates incorrect code for a return statement inside a for loop in an internal function called two or more internal calls deep, producing an invalid jump destination stack underflow. Affected contracts revert such calls unnecessarily, which in limited...

6.3CVSS5.8AI score0.00284EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/21 12:36 a.m.•21 views

CVE-2020-37286 Vyper 0.1.0b4 before 0.3.0 Memory Corruption via Nested Internal Function Calls

Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls. Contracts using such calls as tuple elements, call arguments, or builtin arguments like concat or ecrecover can...

8.3CVSS0.00284EPSS
SaveExploits0References2
Mend
Mend
•added 2026/10/21 12:36 a.m.•6 views

CVE-2020-37286

Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls. Contracts using such calls as tuple elements, call arguments, or builtin arguments like concat or ecrecover can...

8.3CVSS6AI score0.00284EPSS
SaveExploits0References2
CVE
CVE
•added 2026/10/21 12:36 a.m.•9 views

CVE-2020-37286

Vyper versions 0.1.0b4 before 0.3.0 are vulnerable to a memory corruption issue caused by an incorrect stack tip pointer . This occurs when internal function calls are nested within tuples or other nested calls. Consequently, contracts using these calls as tuple elements, call arguments, or as ar...

8.3CVSS6AI score0.00284EPSS
SaveExploits0References2
EUVD
EUVD
•added 2026/10/21 12:36 a.m.•6 views

EUVD-2020-31282

Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls. Contracts using such calls as tuple elements, call arguments, or builtin arguments like concat or ecrecover can...

8.3CVSS6AI score0.00284EPSS
SaveExploits0References2
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•7 views

PT-2026-120240

Vyper 0.1.0b1 before 0.1.0b12, 0.1.0b14, and 0.4.1 through 0.5.0b1 mix character-based line offsets with Python's UTF-8 byte col offset values in vyper/ast/parse.py, so multi-byte characters shift the source slices used to reconstruct later numeric literals. An attacker contributing source with...

6CVSS6AI score0.00183EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•5 views

PT-2026-120157

Vyper from 0.1.0b10 before 0.2.3 generates incorrect code for a return statement inside a for loop in an internal function called two or more internal calls deep, producing an invalid jump destination stack underflow. Affected contracts revert such calls unnecessarily, which in limited...

6.3CVSS5.8AI score0.00284EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•5 views

PT-2026-120242

Vyper 0.1.0b1 before 0.1.0b17 and 0.4.1 through 0.5.0b1 builds its source-line table with str.splitlines, which treats characters like form feed and U+2028 as line breaks the Python parser ignores, so numeric literals are classified and validated from shifted source text. An attacker contributing...

6CVSS5.9AI score0.00183EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•6 views

PT-2026-120156

Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts passing multi-dimensional arrays or structs to internal or external functions receive corrupted values because the...

8.2CVSS6.1AI score0.00251EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•6 views

PT-2026-120244

Vyper 0.3.4 through 0.5.0b1 computes the remaining blueprint size in create from blueprint by uint256 subtraction without first checking that code offset is below the blueprint's code size, so a huge offset wraps to a small positive value. An attacker controlling code offset can make a factory...

6.3CVSS6AI score0.00201EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•4 views

PT-2026-120158

Vyper before 0.3.1 lacks a uint8 type, allowing interface return values declared as uint8, such as ERC20.decimals, to be stored in uint256 variables without bounds checking. Malicious contracts can return values greater than 255 to manipulate or bypass contract logic that relies on these values...

6.3CVSS5.9AI score0.00261EPSS
SaveExploits0References3
Positive Technologies
Positive Technologies
•added 2026/10/21 12:00 a.m.•6 views

PT-2026-120161

Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls are performed inside arrays. Contracts placing internal calls in nested array elements, external call arguments, struct literals, or raw log topics can...

8.3CVSS6.1AI score0.00284EPSS
SaveExploits0References3
Rows per page
Query Builder