TransparentUpgradeableProxy clashing selector calls may not be delegated in @openzeppelin/contracts
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 secure smart contract development. A function in the implementation contract may be inaccessible if its selector clashes with one of the proxy's own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata. The probability of an accidental clash is negligible, but one could be caused deliberately and could cause a reduction in availability. The issue has been fixed in version 4.8.3. As a workaround if a function appears to be inaccessible for this reason, it may be possible to craft the calldata such that ABI decoding does not fail at the proxy and the function is properly proxied through.
From the CVE record · GitHub_M
A function in an implementation contract can become inaccessible when its selector clashes with a proxy function whose signature has incompatible ABI encoding. A deliberately caused clash can make the proxy revert while decoding calldata, reducing availability; the input does not specify authentication or user-interaction requirements.
Teams using npm @openzeppelin/contracts or @openzeppelin/contracts-upgradeable versions >=3.2.0 and <4.8.3 should check their deployments.