CVE-2023-42460: medium-severity vulnerability in vyperlang vyper
_abi_decode input not validated in complex expressions in Vyper
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.7%
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 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Affected products
vyperlang · vyperRelated CVEs — vyperlang vyper
In the same product, most dangerous first.
CVE-2024-24563CRITICALVyper array negative index vulnerabilityEPSS 1.5%CVE-2022-24845HIGHInteger bounds error in VyperEPSS 1.4%CVE-2022-29255HIGHMultiple evaluation of contract address in call in vyperEPSS 1.3%CVE-2023-31146HIGHVyper vulnerable to OOB DynArray access when array is on both LHS and RHS of an assignmentEPSS 1.3%CVE-2021-41121HIGHMemory corruption in VyperEPSS 1.1%CVE-2022-24787HIGHIncorrect Comparison in VyperEPSS 1.0%