Skip to content

UUPSUpgradeable vulnerability in @openzeppelin/contracts

Critical severity GitHub Reviewed Published Sep 14, 2021 in OpenZeppelin/openzeppelin-contracts • Updated Jan 28, 2023

Package

npm @openzeppelin/contracts (npm)

Affected versions

>= 4.1.0, < 4.3.2

Patched versions

4.3.2
npm @openzeppelin/contracts-upgradeable (npm)
>= 4.1.0, < 4.3.2
4.3.2

Description

Impact

Upgradeable contracts using UUPSUpgradeable may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.

Patches

A fix is included in version 4.3.2 of @openzeppelin/contracts and @openzeppelin/contracts-upgradeable.

Workarounds

Initialize implementation contracts using UUPSUpgradeable by invoking the initializer function (usually called initialize). An example is provided in the forum.

References

Post-mortem.

For more information

If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at [email protected].

References

@frangio frangio published to OpenZeppelin/openzeppelin-contracts Sep 14, 2021
Reviewed Sep 14, 2021
Published to the GitHub Advisory Database Sep 15, 2021
Published by the National Vulnerability Database Nov 12, 2021
Last updated Jan 28, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.352%
(72nd percentile)

Weaknesses

CVE ID

CVE-2021-41264

GHSA ID

GHSA-5vp3-v4hc-gx76

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.