Security readout for executives and security teams
Plain-English summary
A helper used by some smart contracts to check signatures could fail unexpectedly instead of returning “invalid.” If business logic depends on that non-reverting behavior, affected contracts may make the wrong decision or halt a flow. This is mainly relevant to teams using OpenZeppelin Contracts SignatureChecker in affected versions.
Executive priority
Treat as high priority for Web3 products where signature validation gates value movement, permissions, or account actions. Not every OpenZeppelin user is exposed; urgency depends on actual SignatureChecker use and upgradeability.
Technical view
OpenZeppelin Contracts versions >=4.1.0 and <4.7.1 have a SignatureChecker.isValidSignatureNow issue involving invalid or nonconforming EIP-1271 signer contracts. An abi.decode assumption can cause a revert where callers expect false. Impact depends on downstream logic that treats invalid signatures differently from reverted checks.
Likely exposure
Exposure is limited to smart contracts using OpenZeppelin Contracts SignatureChecker from >=4.1.0 and <4.7.1, especially where invalid signatures are intentionally handled without reverting.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Abuse would depend on reachable contract logic that accepts an unexpected revert as a meaningful state change or failure mode.
Researcher notes
The key condition is not just dependency version, but caller semantics around invalid signatures. Focus review on EIP-1271 contract-signature validation, revert handling, and paths where false versus revert changes authorization or state behavior.
Mitigation direction
- Upgrade OpenZeppelin Contracts to 4.7.1 or later.
- Review SignatureChecker.isValidSignatureNow call sites for non-reverting invalid-signature assumptions.
- Assess upgrade, redeploy, or proxy-governance paths for already deployed contracts.
- Check OpenZeppelin advisory and PR 3552 for vendor-specific fix context.
Validation and detection
- Inventory package versions used at build time and in deployed contract source metadata.
- Search contracts for SignatureChecker.isValidSignatureNow usage.
- Test invalid EIP-1271 signer behavior against expected false-return paths.
- Confirm patched library behavior in unit or fork tests before deployment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-4g63-c64m-25w9CVE reference · x_refsource_CONFIRM
- https://github.com/OpenZeppelin/openzeppelin-contracts/pull/3552CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.