GovernorCompatibilityBravo incorrect ABI encoding may lead to unexpected behavior
Impact
The GovernorCompatibilityBravo module may lead to the creation of governance proposals that execute function calls with incorrect arguments due to bad ABI encoding. This happens if the proposal is created using explicit function signatures, e.g. a proposal to invoke the function foo(uint256) is created as propose([target], [0], ["foo(uint256)"], ["0x00..01"]). If the function selector is provided as part of the encoded proposal data the issue is not present, e.g. the same proposal is created as propose([target], [0], ["0x2fbebd3800..01"]), where 2fbebd38 is the function selector.
We've assessed the instances of this contract found on chain, and did not find any occurrence of this bug in the past. Proposal creation through Tally or OpenZeppelin Defender is not affected. The core Governor contract on its own is not affected.
Patches
A fix is included in version v4.4.2 of @openzeppelin/contracts and @openzeppelin/contracts-upgradeable.
Workarounds
Do not create proposals using explicit function signatures. Instead, use the propose function without the signatures argument, and create the proposal using the fully ABI-encoded function call including the function selector in the calldatas argument as explained above.
References
https://github.com/OpenZeppelin/openzeppelin-contracts/issues/3099
Credits
This issue was identified and reported by @GeraldHost.
For more information
If you have any questions, comments, or need assistance regarding this advisory, email us at security@openzeppelin.com.
To submit security reports please use our bug bounty on Immunefi.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | @openzeppelin/contracts | >= 4.3.0, < 4.4.2 | 4.4.2 |
| Paquete de npm | @openzeppelin/contracts-upgradeable | >= 4.3.0, < 4.4.2 | 4.4.2 |
Referencias
- Debilidad (CWE)
-- Plataforma
- npm
- Paquete
@openzeppelin/contracts, @openzeppelin/contracts-upgradeable- Publicada
- 13.01.2022
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-m6w8-fq7v-ph4m - CC BY 4.0
Historial de vulnerabilidades: @openzeppelin/contracts
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 20
- Primera → última
- 08.2021 07.2025
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 2
- Alta 5
- Media 12
- Baja 1
Divulgaciones por año
- 2021: 4
- 2022: 7
- 2023: 7
- 2024: 1
- 2025: 1
- 2026: 0
-
GovernorCompatibilityBravo incorrect ABI encoding may lead to unexpected behavior esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.