CVE-2023-42460
Vyperlang Vyper 0.3.4 – 0.3.10
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-42460 is a medium-severity Incorrect Calculation (CWE-682) vulnerability in Vyperlang Vyper. Its CVSS base score is 5.3 (Medium).
Operationally, ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0268
Vulnerability Data
Vyper is a Pythonic Smart Contract Language for the EVM. The `_abi_decode()` function does not validate input when it is nested in an expression. Uses of `_abi_decode()` can be constructed which allow for bounds checking to be bypassed resulting in…
more
incorrect results. This issue has not yet been fixed, but a fix is expected in release `0.3.10`. Users are advised to reference pull request #3626.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates verification steps that catch incorrect calculations before they reach production.
A.8.26 requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified during development or acquisition; it does not itself enforce correct calculations or stop an arithmetic error from being introduced or exploited.
A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, and design reviews) but does not itself remove or rewrite an incorrect calculation already present in first-party code; that is a code defect class reached only by testing or remediation controls per the locus rule.
Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.
Security testing in development and acceptance can detect calculation flaws before deployment.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-682, a pillar-level weakness, and none of its children carries one either.