Vulnerability in Vyperlang Vyper
CVE-2023-41052
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 3.7 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS: 0.005 (42.9th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 43rd percentile — 42.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.005 · newest: 0.005 · change: +0.001
Affected products
- Vyperlang Vyper — versions <= 0.3.9
Weakness classification (CWE)
References
- github.com/vyperlang/vyper/security/advisories/GHSA-4hg4-9mf5-wxxq (Exploit, Patch, Third Party Advisory)
- github.com/vyperlang/vyper/pull/3583 (Patch)
Frequently asked questions
- What is CVE-2023-41052?
- CVE-2023-41052 is a low-severity vulnerability in Vyperlang Vyper, classified under Always-Incorrect Control Flow Implementation. CVSS score: 3.7/10. Published 2023-09-04.
- How severe is CVE-2023-41052?
- Low severity. CVSS v3 base score is 3.7 out of 10.