CVE-2023-39363 – vyper

Package

Manager: pip
Name: vyper
Vulnerable Version: >=0.2.15 <0.3.1

Severity

Level: Critical

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:A

EPSS: 0.00072 pctl0.22552

Details

Vyper has incorrectly allocated named re-entrancy locks ### Impact 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: - A `.vy` contract compiled with either of the following `vyper` versions: `0.2.15`, `0.2.16`, `0.3.0` - A primary function that utilizes the `@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) - A secondary function that utilizes the same `key` and would be affected by the improper state caused by the primary function ### Patches https://github.com/vyperlang/vyper/pull/2439, https://github.com/vyperlang/vyper/pull/2514 ### Workarounds Upgrade to 0.3.1 or higher ### References Technical post-mortem report: https://hackmd.io/@vyperlang/HJUgNMhs2

Metadata

Created: 2023-08-09T14:27:57Z
Modified: 2024-10-11T14:04:46Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/08/GHSA-5824-cm3x-3c38/GHSA-5824-cm3x-3c38.json
CWE IDs: ["CWE-863"]
Alternative ID: GHSA-5824-cm3x-3c38
Finding: F006
Auto approve: 1