OpenZeppelin Contracts's SignatureChecker may revert on invalid EIP-1271 signers
openzeppelin-contracts
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| @openzeppelin/contracts-upgradeable npm |
|
|
openzeppelin-contracts
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| @openzeppelin/contracts-upgradeable npm |
|
|
OpenZeppelin Contracts is a library for smart contract development. Versions 4.1.0 until 4.7.1 are vulnerable to the SignatureChecker reverting. `SignatureChecker.isValidSignatureNow` is not expected to 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-1271 as expected. The contracts that may be affected are those that use `SignatureChecker` to check the validity of a signature and handle invalid signatures in a way other than reverting. The issue was patched in version 4.7.1.
From the CVE record · GitHub_M
SignatureChecker.isValidSignatureNow can unexpectedly revert when checking a target contract that does not implement EIP-1271 as expected. This can disrupt contracts that handle invalid signatures without reverting. The input does not specify attacker access requirements or user interaction.
Teams using npm @openzeppelin/contracts or @openzeppelin/contracts-upgradeable versions 4.1.0 through versions before 4.7.1 should check their contracts.