CVE-2023-40015
LOWDescription
Vyper is a Pythonic Smart Contract Language. For the following (probably non-exhaustive) list of expressions, the compiler evaluates the arguments from right to left instead of left to right. `unsafe_add, unsafe_sub, unsafe_mul, unsafe_div, pow_mod256, |, &, ^ (bitwise operators), bitwise_or (deprecated), bitwise_and (deprecated), bitwise_xor (deprecated), raw_call, <, >, <=, >=, ==, !=, in, not in (when lhs and rhs are enums)`. This behaviour becomes a problem when the evaluation of one of the arguments produces side effects that other arguments depend on. The following expressions can produce side-effect: state modifying external call , state modifying internal call, `raw_call`, `pop()` when used on a Dynamic Array stored in the storage, `create_minimal_proxy_to`, `create_copy_of`, `create_from_blueprint`. This issue has not yet been patched. Users are advised to 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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 34% of all known CVEs.
References
Related Vulnerabilities
Other CWE-670 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-9425 | High | 7.5 | 17% | - | Fix |
| CVE-2019-9946 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-32896 | High | 7.8 | 3.0% | KEV | - |
| CVE-2019-17192 | Critical | 9.8 | 2.7% | - | - |
| CVE-2026-38361 | High | 7.5 | 2.6% | - | - |
| CVE-2020-1914 | Critical | 9.8 | 2.5% | - | Fix |
Common questions
How do I fix CVE-2023-40015?
No published fix for CVE-2023-40015 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2023-40015 being actively exploited?
Not that we know of. CVE-2023-40015 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.42% is the estimated probability that it will be exploited in the next 30 days. That is higher than 34% of all scored CVEs.
How severe is CVE-2023-40015?
CVE-2023-40015 has a CVSS v3 base score of 3.7, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2023-40015
Markdown
[](https://tridentstack.com/cve/CVE-2023-40015)HTML
<a href="https://tridentstack.com/cve/CVE-2023-40015"><img src="https://tridentstack.com/cve/badge/CVE-2023-40015.svg" alt="CVE-2023-40015"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.