Skip to content
Sign in
CVE-2023-424415.3MediumCWE-833

CVE-2023-42441: Vyper has incorrect re-entrancy lock when key is empty string

vyperlang · vyper

Affected: vyperlang · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days
44th percentile
050100

Higher than 44% of scored CVEs

5.3MediumCVSS 3.1
LowMedium

DescriptionCVE.org

Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). Starting in version 0.2.9 and prior to version 0.3.10, locks of the type `@nonreentrant("")` or `@nonreentrant('')` do not produce reentrancy checks at runtime. This issue is fixed in version 0.3.10. As a workaround, ensure the lock name is a non-empty string.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • vyperlang · vyper>= 0.2.9, < 0.3.10

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
vyperlang

CoverageNo articles yet

No CyberSIXT article names CVE-2023-42441 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in