CVE-2022-31170

OpenZeppelin Contracts's ERC165Checker may revert instead of returning false

References

https://github.com/OpenZeppelin/openzeppelin-contracts/pull/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].

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-31170 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.7.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue was patched in 4.7.1.

1. What is CVE-2022-31170? CVE-2022-31170 is a high-severity improper input validation vulnerability in @openzeppelin/contracts (npm), affecting versions >= 4.0.0, < 4.7.1. It is fixed in 4.7.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-31170? CVE-2022-31170 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-31170?
   • @openzeppelin/contracts (npm) (versions >= 4.0.0, < 4.7.1)
   • @openzeppelin/contracts-upgradeable (npm) (versions >= 4.0.0, < 4.7.1)
4. Is there a fix for CVE-2022-31170? Yes. CVE-2022-31170 is fixed in 4.7.1. Upgrade to this version or later.
5. Is CVE-2022-31170 exploitable, and should I be worried? Whether CVE-2022-31170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31170 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31170?
   • Upgrade @openzeppelin/contracts to 4.7.1 or later
   • Upgrade @openzeppelin/contracts-upgradeable to 4.7.1 or later

Other vulnerabilities in @openzeppelin/contracts