First published: Mon Apr 17 2023(Updated: )
### Impact 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. ### Patches The issue has been fixed in v4.8.3. ### Workarounds 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. ### References https://github.com/OpenZeppelin/openzeppelin-contracts/pull/4154
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@openzeppelin/contracts-upgradeable | >=3.2.0<4.8.3 | 4.8.3 |
npm/@openzeppelin/contracts | >=3.2.0<4.8.3 | 4.8.3 |
OpenZeppelin Contracts | >=3.2.0<4.8.3 | |
OpenZeppelin Contracts Upgradeable | >=3.2.0<4.8.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-30541.
OpenZeppelin Contracts is a library for secure smart contract development.
The severity of CVE-2023-30541 is medium.
CVE-2023-30541 affects OpenZeppelin Contracts versions 3.2.0 to 4.8.3.
You can fix CVE-2023-30541 by updating to OpenZeppelin Contracts version 4.8.3 or later.