CVE-2023-42441Medium· 5.3▾ SunlitVyper has incorrect re-entrancy lock when key is empty string
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.2 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.4%
0.4% → 0.5%
Locks of the type @nonreentrant("") or @nonreentrant('') do not produce reentrancy checks at runtime.
@nonreentrant("") # unprotected
@external
def bar():
pass
@nonreentrant("lock") # protected
@external
def foo():
pass
Patched in #3605
The lock name should be a non-empty string.
Are there any links users can visit to find out more?
vyper >= 0.2.9, < 0.3.10Upgrade to a patched release:
vyper 0.3.10Connected by shared product, vendor, weakness, or advisory.
CVE-2024-24567Medium· 4.8Vyper's raw_call `value=` kwargs not disabled for static and delegate calls
CVE-2023-30629High· 7.5Incorrect success value returned in vyper
CVE-2025-21607LowVyper Does Not Check the Success of Certain Precompile Calls
CVE-2023-32059High· 7.5Vyper vulnerable to incorrect ordering of arguments for kwargs passed to internal calls
CVE-2023-30837High· 7.5vyper vulnerable to storage allocator overflow
CVE-2024-24560Low· 3.7Vyper's external calls can overflow return data to return input buffer