CVE-2023-30541 json
TransparentUpgradeableProxy clashing selector calls may not be delegated in @openzeppelin/contracts
published 3y ago modified 2mo ago also EUVD-2023-1359 , GHSA-mx2q-35m2-x2rh
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @openzeppelin/contracts 4.8.3
- npm @openzeppelin/contracts-upgradeable 4.8.3
- openzeppelin contracts 4.8.3
- openzeppelin contracts_upgradeable 4.8.3
Is CVE-2023-30541 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @openzeppelin/contracts | >=3.2.0, <4.8.3 |
4.8.3 |
| npm | @openzeppelin/contracts-upgradeable | >=3.2.0, <4.8.3 |
4.8.3 |
Affected products
- OpenZeppelin openzeppelin-contracts
Classification
- Weakness
-
- CWE-436 Interpretation Conflict
References
-
github.com
/OpenZeppelin/openzeppelin-contracts/pull/4154
web, patch
-
github.com
/OpenZeppelin/openzeppelin-contracts-upgradeable/commit/58fa0f81c4036f1a3b616fdffad2fd27e5d5ce21
web
-
github.com
/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-mx2q-35m2-x2rh
web, vendor-advisory, advisory
-
github.com
/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.8.3
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-30541
advisory
-
github.com
/OpenZeppelin/openzeppelin-contracts
package
Sources
- CVE List CVE-2023-30541
- GitHub Advisory GHSA-mx2q-35m2-x2rh
- NVD CVE-2023-30541
- Maintainer advisory GHSA-mx2q-35m2-x2rh
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of OpenZeppelin/openzeppelin-contracts published their own advisory on GitHub. Reviewed sources take precedence over it.