CVE-2022-39384
Summary
| CVE | CVE-2022-39384 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-11-04 22:15:00 UTC |
| Updated | 2022-12-06 19:51:00 UTC |
| Description | OpenZeppelin Contracts is a library for secure smart contract development. Before version 4.4.1 but after 3.2.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 in the scenario described above, breaking the expectation that there is a single execution. Note that upgradeable proxies are commonly initialized together with contract creation, where reentrancy is not feasible, so the impact of this issue is believed to be minor. This issue has been patched, please upgrade to version 4.4.1. As a workaround, avoid untrusted external calls during initialization. |
Risk And Classification
Problem Types: CWE-665
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Openzeppelin | Contracts | All | All | All | All |
| Application | Openzeppelin | Contracts-upgradeable | All | All | All | All |
| Application | Openzeppelin | Contracts Upgradeable | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Update initializer modifier to prevent reentrancy during initialization by Amxx · Pull Request #3006 · OpenZeppelin/openzeppelin-contracts · GitHub | MISC | github.com | |
| Initializer reentrancy may lead to double initialization · Advisory · OpenZeppelin/openzeppelin-contracts · GitHub | CONFIRM | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.