In versions 0.2.15, 0.2.16 and 0.3.0, named re-entrancy locks are allocated incorrectly. Each function using a named re-entrancy lock gets a unique lock regardless of the key, allowing cross-function re-entrancy in contracts compiled with the susceptible versions. A specific set of conditions is required to result in misbehavior of affected contracts, specifically:
.vy
contract compiled with either of the following vyper
versions: 0.2.15
, 0.2.16
, 0.3.0
@nonreentrant
decorator with a specific key
and does not strictly follow the check-effects-interaction pattern (i.e. contains an external call to an untrusted party before storage updates)key
and would be affected by the improper state caused by the primary functionhttps://github.com/vyperlang/vyper/pull/2439, https://github.com/vyperlang/vyper/pull/2514
Upgrade to 0.3.1 or higher
Technical post-mortem report: https://hackmd.io/@vyperlang/HJUgNMhs2
{ "nvd_published_at": "2023-08-07T19:15:11Z", "cwe_ids": [ "CWE-863" ], "severity": "CRITICAL", "github_reviewed": true, "github_reviewed_at": "2023-08-09T14:27:57Z" }