Contract reentrancy via omitted default-function locks
Published Apr 25, 2024 · Updated Aug 2, 2024
Improper locking in Vyper before 0.3.0 allows remote attackers to bypass reentrancy protection in compiled contracts via a default function. The code generator accepts @nonreentrant on default but emits the fallback path without the requested storage lock. Exploitation requires a deployed contract compiled by an affected release with a decorated default function; the vendor's search found none in production.
Summary
What happened
Improper locking in Vyper before 0.3.0 allows remote attackers to bypass reentrancy protection in compiled contracts via a default function. The code generator accepts @nonreentrant on default but emits the fallback path without the requested storage lock. Exploitation requires a deployed contract compiled by an affected release with a decorated default function; the vendor's search found none in production.
The record
- CVE
- CVE-2024-32648
- Published
- Apr 25, 2024
- Updated
- Aug 2, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-667
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=*
- Affected versionversion=< 0.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor lock-omission proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo