Vyper
Vyper 0.4.0b1 through 0.5.0b1 Name Shadowing of Imported Constants and Default Arguments
Vyper 0.4.0b1 through 0.5.0b1 miscompiles unfoldable constants and omitted default arguments from imported modules, because parse_Name resolves their names in the using function's scope rather than at declaration. When a contract's parameter, local, or loop variable shares such a name, attacker-influenced input can replace the intended value, including out-of-range values for narrow types such as uint8, corrupting validation or accounting logic.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.6high · scored by CNA · CWE-706
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
vyperlang vyper
- >= 0.4.0b1, <= 0.5.0b1
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/vyperlang/vyper/security/advisories…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.