CVE-2022-31198
Summary
| CVE | CVE-2022-31198 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-08-01 21:15:00 UTC |
| Updated | 2022-12-06 19:51:00 UTC |
| Description | OpenZeppelin Contracts is a library for secure smart contract development. This issue concerns instances of Governor that use the module `GovernorVotesQuorumFraction`, a mechanism that determines quorum requirements as a percentage of the voting token's total supply. In affected instances, when a proposal is passed to lower the quorum requirements, past proposals may become executable if they had been defeated only due to lack of quorum, and the number of votes it received meets the new quorum requirement. Analysis of instances on chain found only one proposal that met this condition, and we are actively monitoring for new occurrences of this particular issue. This issue has been patched in v4.7.2. Users are advised to upgrade. Users unable to upgrade should consider avoiding lowering quorum requirements if a past proposal was defeated for lack of quorum. |
Risk And Classification
Problem Types: CWE-682
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Openzeppelin | Contracts | All | All | All | All |
| Application | Openzeppelin | Contracts-upgradeable | All | All | All | All |
| Application | Openzeppelin | Contracts Upgradeable | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| GovernorVotesQuorumFraction updates to quorum may affect past defeated proposals · Advisory · OpenZeppelin/openzeppelin-contracts · GitHub | CONFIRM | github.com | |
| Keep track of historical quorum values by Amxx · Pull Request #3561 · OpenZeppelin/openzeppelin-contracts · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.