Unbounded gas consumption in @openzeppelin/contracts
openzeppelin-contracts
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| openzeppelin-solidity npm |
| No fix yet |
| @openzeppelin/contracts-upgradeable npm |
openzeppelin-contracts
| Product | Affected | Fixed in |
|---|---|---|
| @openzeppelin/contracts npm |
|
|
| openzeppelin-solidity npm |
| No fix yet |
| @openzeppelin/contracts-upgradeable npm |
≥ 3.2.0 · < 4.7.2
|
| openzeppelin-eth npm |
| No fix yet |
OpenZeppelin Contracts is a library for secure smart contract development. The target contract of an EIP-165 `supportsInterface` query can cause unbounded gas consumption by returning a lot of data, while it is generally assumed that this operation has a bounded cost. The issue has been fixed in v4.7.2. Users are advised to upgrade. There are no known workarounds for this issue.
From the CVE record · GitHub_M
An EIP-165 `supportsInterface` query can consume unbounded gas if the target contract returns a large amount of data. This occurs when a contract queries such a target; the input does not specify authentication requirements or other user interaction.
Check projects using npm @openzeppelin/contracts >=2.0.0 <4.7.2, @openzeppelin/contracts-upgradeable >=3.2.0 <4.7.2, openzeppelin-solidity >=2.0.0 <=4.6.0, or openzeppelin-eth >=2.0.0 <=2.2.0.