Skip to content

OpenZeppelin Contracts's ERC165Checker may revert instead of returning false

High severity GitHub Reviewed Published Jul 20, 2022 in OpenZeppelin/openzeppelin-contracts • Updated Jan 30, 2023

Package

npm @openzeppelin/contracts (npm)

Affected versions

>= 4.0.0, < 4.7.1

Patched versions

4.7.1
npm @openzeppelin/contracts-upgradeable (npm)
>= 4.0.0, < 4.7.1
4.7.1

Description

Impact

ERC165Checker.supportsInterface is designed to always successfully return a boolean, and under no circumstance revert. However, an incorrect assumption about Solidity 0.8's abi.decode allows some cases to revert, given a target contract that doesn't implement EIP-165 as expected, specifically if it returns a value other than 0 or 1.

The contracts that may be affected are those that use ERC165Checker to check for support for an interface and then handle the lack of support in a way other than reverting.

Patches

The issue was patched in 4.7.1.

References

OpenZeppelin/openzeppelin-contracts#3552

For more information

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

References

@frangio frangio published to OpenZeppelin/openzeppelin-contracts Jul 20, 2022
Published to the GitHub Advisory Database Jul 21, 2022
Reviewed Jul 21, 2022
Published by the National Vulnerability Database Jul 22, 2022
Last updated Jan 30, 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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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:N/I:H/A:N

EPSS score

0.062%
(28th percentile)

Weaknesses

CVE ID

CVE-2022-31170

GHSA ID

GHSA-qh9x-gcfh-pcrw

Source code

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