Improper Initialization in OpenZeppelin
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| @openzeppelin/contracts-upgradeable npm |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| @openzeppelin/contracts-upgradeable npm |
|
|
In OpenZeppelin <=v4.4.0, initializer functions that are invoked separate from contract creation (the most prominent example being minimal proxies) may be reentered if they make an untrusted non-view external call. Once an initializer has finished running it can never be re-executed. However, an exception put in place to support multiple inheritance made reentrancy possible, breaking the expectation that there is a single execution.
From the CVE record · mitre
OpenZeppelin initializer functions invoked separately from contract creation may be reentered if they make an untrusted non-view external call. This can break the expectation that an initializer runs only once. The input does not specify authentication requirements or user interaction.
Engineers using npm @openzeppelin/contracts or @openzeppelin/contracts-upgradeable versions >=3.2.0 and <4.4.1 should check their deployments.