Vyper vulnerable to incorrect ordering of arguments for kwargs passed to internal calls
### Impact Internal calls to internal functions with more than 1 default argument 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. In the `bar()` function in the following code, `self.foo(13)` is compiled to `self.foo(13,12)` instead of `self.foo(13,1337)`. ```vyper @internal def foo(a:uint256 = 12, b:uint256 = 1337): pass @internal def bar(): self.foo(13) ``` note that at the time of publication, the ability to pass kwargs to internal functions is an undocumented feature that does not seem to be widely used. ### Patches patched in c3e68c302aa6e1429946473769dd1232145822ac ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ ### References _Are there any links users can visit to find out more?_
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-32059US | high7.5 | — | ||
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 t… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-79.yamlWEB
- https://github.com/vyperlang/vyperPACKAGE
- https://github.com/vyperlang/vyper/commit/c3e68c302aa6e1429946473769dd1232145822acWEB
- https://github.com/vyperlang/vyper/security/advisories/GHSA-ph9x-4vc9-m39gWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-32059ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan