# CVE-2021-46320: Other in n/a

> Reentrancy in OpenZeppelin initializer functions allows attackers to manipulate contract state during initialization, potentially leading to unauthorized code execution or data modification.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2022
- **Updated:** 4 Aug 2024

## What is CVE-2021-46320?

CVE-2021-46320 is a high-severity vulnerability in n/a, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2021-46320?

It affects 1 product.


Products: Openzeppelin Openzeppelin.

## How do I fix CVE-2021-46320?

Upgrade to a fixed version.

## Is CVE-2021-46320 being exploited?

There is no known exploitation of CVE-2021-46320 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46320 and fix it if it is affected.

What it is: CVE-2021-46320 is a high-severity vulnerability in n/a, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46320 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-46320/ (Markdown: https://insights.sbomify.com/CVE-2021-46320/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-46320
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-46320
- OSV: https://osv.dev/vulnerability/CVE-2021-46320

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-46320/
Summaries are generated and may contain mistakes; the official description above is the record.