Governor proposal creation may be blocked by frontrunning in OpenZeppelin
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 smart contract development. By frontrunning the creation of a proposal, an attacker can become the proposer and gain the ability to cancel it. The attacker can do this repeatedly to try to prevent a proposal from being proposed at all. This impacts the `Governor` contract in v4.9.0 only, and the `GovernorCompatibilityBravo` contract since v4.3.0. This problem has been patched in 4.9.1 by introducing opt-in frontrunning protection. Users are advised to upgrade. Users unable to upgrade may submit the proposal creation transaction to an endpoint with frontrunning protection as a workaround.
From the CVE record · GitHub_M
An attacker who frontruns proposal creation can become the proposer and cancel the proposal, potentially repeating this to prevent it from being proposed. This affects `Governor` in v4.9.0 and `GovernorCompatibilityBravo` since v4.3.0; the input does not specify authentication or user-interaction requirements.
Teams using npm `@openzeppelin/contracts` or `@openzeppelin/contracts-upgradeable` versions >=4.3.0 and <4.9.1 should check whether they use the affected Governor contracts.