cve.bz

CVE-2022-39384 openzeppelin: Improper Initialization

5.6 mediumEPSS 0.7%Fix available

Medium (5.6) in openzeppelin. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in @openzeppelin/contracts 4.4.1.

On this page
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.

Severity

CVSS 3.1

5.6 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.7% (unchanged from 0.7% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-665 Improper Initialization
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-39384 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-39384?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-39384?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-39384 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openzeppelin:contractsfrom 3.2.0 before 4.4.1
openzeppelin:contracts_upgradeablefrom 3.2.0 before 4.4.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-88g8-f5mf-f5rjnpm@openzeppelin/contracts<4.4.14.4.1
GHSA-9c22-pwxw-p6hxnpm@openzeppelin/contracts>=3.2.0 <4.4.14.4.1
GHSA-9c22-pwxw-p6hxnpm@openzeppelin/contracts-upgradeable>=3.2.0 <4.4.14.4.1

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON