What is GHSA-93hq-5wgc-jc82?

GHSA-93hq-5wgc-jc82 is a security advisory published by GitHub Security Advisories with High severity. GovernorCompatibilityBravo may trim proposal calldata

Which CVE IDs does GHSA-93hq-5wgc-jc82 cover?

GHSA-93hq-5wgc-jc82 covers the following CVE IDs: CVE-2023-30542. Each CVE has its own detail page on EchelonGraph Pulse with the synthesized EG score.

What is the CVSS v3 score of GHSA-93hq-5wgc-jc82?

GHSA-93hq-5wgc-jc82 has a CVSS v3 base score of 8.8, published by GitHub Security Advisories.

Which products are affected by GHSA-93hq-5wgc-jc82?

GHSA-93hq-5wgc-jc82 affects 2 products, including: npm/@openzeppelin/contracts:\u003e= 4.3.0, \u003c 4.8.3; npm/@openzeppelin/contracts-upgradeable:\u003e= 4.3.0, \u003c 4.8.3.

GHSA-93hq-5wgc-jc82HighCVSS 8.8

GovernorCompatibilityBravo may trim proposal calldata

Vendor

GitHub Security Advisories

Published

April 20, 2023

Last Modified

April 27, 2023

🔗 CVE IDs covered (1)

CVE-2023-30542 →

📋 Description

Impact

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.

Patches

This issue has been patched in v4.8.3.

Workarounds

Ensure that all proposals that pass through governance have equal length signatures and calldatas parameters.

🎯 Affected products2

npm/@openzeppelin/contracts:>= 4.3.0, < 4.8.3
npm/@openzeppelin/contracts-upgradeable:>= 4.3.0, < 4.8.3