CVE-2023-30542 json
GovernorCompatibilityBravo may trim proposal calldata
published 3y ago modified 4mo ago also EUVD-2023-1247 , GHSA-93hq-5wgc-jc82
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
OpenZeppelin Contracts is a library for secure smart contract development. The proposal creation entrypoint (`propose`) in `GovernorCompatibilityBravo` allows the creation of proposals with a `signatures` array shorter than the `calldatas` array. This causes the additional elements of the latter to be ignored, and if the proposal succeeds the corresponding actions would eventually execute without any calldata. The `ProposalCreated` event correctly represents what will eventually execute, but the proposal parameters as queried through `getActions` appear to respect the original intended calldata. This issue has been patched in 4.8.3. As a workaround, ensure that all proposals that pass through governance have equal length `signatures` and `calldatas` parameters.
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-30542 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
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @openzeppelin/contracts | >=4.3.0, <4.8.3 |
4.8.3 |
| npm | @openzeppelin/contracts-upgradeable | >=4.3.0, <4.8.3 |
4.8.3 |
Affected products
- OpenZeppelin openzeppelin-contracts
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/OpenZeppelin/openzeppelin-contracts/commit/8d633cb7d169f2f8595b273660b00b69e845c2fe
web
-
github.com
/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-93hq-5wgc-jc82
web, vendor-advisory, advisory
-
github.com
/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.8.3
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-30542
advisory
-
github.com
/OpenZeppelin/openzeppelin-contracts
package
Sources
- CVE List CVE-2023-30542
- GitHub Advisory GHSA-93hq-5wgc-jc82
- NVD CVE-2023-30542
- Maintainer advisory GHSA-93hq-5wgc-jc82
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.