Call reverts via ill-encoded EIP-1271 responses
Published Jul 21, 2022 · Updated Apr 23, 2025
Improper input validation in OpenZeppelin Contracts 4.1.0 through 4.7.0 allows attackers to force signature-checking calls to revert. SignatureChecker.isValidSignatureNow decodes a 32-byte EIP-1271 return value as bytes4, so Solidity 0.8 rejects nonzero trailing bytes instead of returning false. The condition requires a target signer contract that returns an ill-encoded EIP-1271 value and affects consumers that handle an invalid signature without otherwise reverting.
Summary
What happened
Improper input validation in OpenZeppelin Contracts 4.1.0 through 4.7.0 allows attackers to force signature-checking calls to revert. SignatureChecker.isValidSignatureNow decodes a 32-byte EIP-1271 return value as bytes4, so Solidity 0.8 rejects nonzero trailing bytes instead of returning false. The condition requires a target signer contract that returns an ill-encoded EIP-1271 value and affects consumers that handle an invalid signature without otherwise reverting.
The record
- CVE
- CVE-2022-31172
- Published
- Jul 21, 2022
- Updated
- Apr 23, 2025
- Vendor
- OpenZeppelin
- Product
- OpenZeppelin Contracts
- Classifications
- CWE-347, CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.1.0, < 4.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo