Skip to content

OpenZeppelin Contracts vulnerable to ECDSA signature malleability

High severity GitHub Reviewed Published Aug 10, 2022 in OpenZeppelin/openzeppelin-contracts • Updated Feb 2, 2023

Package

npm @openzeppelin/contracts (npm)

Affected versions

>= 4.1.0, < 4.7.3

Patched versions

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

Description

Impact

The functions ECDSA.recover and ECDSA.tryRecover are vulnerable to a kind of signature malleability due to accepting EIP-2098 compact signatures in addition to the traditional 65 byte signature format. This is only an issue for the functions that take a single bytes argument, and not the functions that take r, v, s or r, vs as separate arguments.

The potentially affected contracts are those that implement signature reuse or replay protection by marking the signature itself as used rather than the signed message or a nonce included in it. A user may take a signature that has already been submitted, submit it again in a different form, and bypass this protection.

Patches

The issue has been patched in 4.7.3.

For more information

If you have any questions or comments about this advisory, or need assistance deploying a fix, email us at [email protected].

References

@frangio frangio published to OpenZeppelin/openzeppelin-contracts Aug 10, 2022
Published by the National Vulnerability Database Aug 15, 2022
Published to the GitHub Advisory Database Aug 18, 2022
Reviewed Aug 18, 2022
Last updated Feb 2, 2023

Severity

High

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
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

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:H/PR:L/UI:R/S:C/C:H/I:H/A:L

EPSS score

0.061%
(28th percentile)

Weaknesses

CVE ID

CVE-2022-35961

GHSA ID

GHSA-4h98-2769-gh6h

Source code

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