Ethereum Vyper up to 0.3.7 function call with incorrect order of arguments
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Ethereum Vyper up to 0.3.7. This impacts an unknown function. This manipulation causes function call with incorrect order of arguments. This vulnerability appears as CVE-2023-32059. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Ethereum Vyper up to 0.3.7. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a function call with incorrect order of arguments vulnerability. The CWE definition for the vulnerability is CWE-683. The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented 05/12/2023 as GHSA-ph9x-4vc9-m39g. The advisory is shared at github.com. This vulnerability is known as CVE-2023-32059 since 05/01/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.3.8 eliminates this vulnerability. Applying the patch c3e68c302aa6e1429946473769dd1232145822ac is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Function call with incorrect order of argumentsCWE: CWE-683
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Vyper 0.3.8
Patch: c3e68c302aa6e1429946473769dd1232145822ac
Timeline
05/01/2023 🔍05/12/2023 🔍
05/12/2023 🔍
05/12/2023 🔍
Sources
Advisory: GHSA-ph9x-4vc9-m39gStatus: Confirmed
CVE: CVE-2023-32059 (🔍)
GCVE (CVE): GCVE-0-2023-32059
GCVE (VulDB): GCVE-100-228853
Entry
Created: 05/12/2023 07:28Changes: 05/12/2023 07:28 (51)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.