Vulnerability · Published Sep 4, 2023 · Assigned by GitHub_M

CVE-2023-41052Vyper: incorrect order of evaluation of side effects for some builtins

Low 3.7

In plain English

A low-severity security flaw in vyper from vyperlang. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 45% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)3.7Low
Exploit odds (30 days)0.5%top 54.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPIvyper0.3.10GHSA-4hg4-9mf5-wxxq
PyPIvyper0.3.10rc1PYSEC-2023-168

Affected products (as reported)

VendorProductVersions
vyperlang vyper <= 0.3.9

Weakness: CWE-670 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References