Contract state manipulation via per-function reentrancy locks
Published Aug 7, 2023 · Updated Oct 11, 2024
Re-entrancy guard failure in Vyper 0.2.15, 0.2.16, and 0.3.0 allows remote attackers to alter affected contract state. The compiler assigns a distinct storage slot to every @nonreentrant-decorated function instead of reusing the slot for a shared key. Exploitation requires two functions sharing a key, an untrusted external call before storage updates, and state that enables token theft or other unauthorized changes.
Summary
What happened
Re-entrancy guard failure in Vyper 0.2.15, 0.2.16, and 0.3.0 allows remote attackers to alter affected contract state. The compiler assigns a distinct storage slot to every @nonreentrant-decorated function instead of reusing the slot for a shared key. Exploitation requires two functions sharing a key, an untrusted external call before storage updates, and state that enables token theft or other unauthorized changes.
The record
- CVE
- CVE-2023-39363
- Published
- Aug 7, 2023
- Updated
- Oct 11, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2023Exploitation reportedCurve liquidity pool exploitation
- Aug 7, 2023CVE publishedPublication date reported by the CVE source.
- Oct 11, 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== 0.2.15
- Affected versionversion== 0.2.16
- 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.
Public exploit references
- Curve pool reentrancy exploit transactionsweaponized · observed in use
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Curve liquidity pool exploitationreported exploitation
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