OpenZeppelin Contracts base64 encoding may read from potentially dirty memory
Impact
The Base64.encode function encodes a bytes input by iterating over it in chunks of 3 bytes. When this input is not a multiple of 3, the last iteration may read parts of the memory that are beyond the input buffer.
Although the encode function pads the output for these cases, up to 4 bits of data are kept between the encoding and padding, corrupting the output if these bits were dirty (i.e. memory after the input is not 0). These conditions are more frequent in the following scenarios:
- A
bytes memorystruct is allocated just after the input and the first bytes of it are non-zero. - The memory pointer is set to a non-empty memory location before allocating the input.
Developers should evaluate whether the extra bits can be maliciously manipulated by an attacker.
Patches
Upgrade to 5.0.2 or 4.9.6.
References
This issue was reported by the Independent Security Researcher Riley Holterhus through Immunefi (@rileyholterhus on X)
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.5.0, < 4.9.6, >= 5.0.0-rc.0, < 5.0.2 | 4.9.6, 5.0.2 |
| Paquete de npm | @openzeppelin/contracts-upgradeable | >= 5.0.0-rc.0, < 5.0.2, >= 4.5.0, < 4.9.6 | 5.0.2, 4.9.6 |
Referencias
- https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-9vx6-7xxf-x967
- https://nvd.nist.gov/vuln/detail/CVE-2024-27094
- https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/commit/2d081f24cac1a867f6f73d512f2022e1fa987854
- https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/commit/723f8cab09cdae1aca9ec9cc1cfa040c2d4b06c1
- https://github.com/OpenZeppelin/openzeppelin-contracts/commit/92224533b1263772b0774eec3134e132a3d7b2a6
- https://github.com/OpenZeppelin/openzeppelin-contracts/commit/a6286d0fded8771b3a645e5813e51993c490399c
- https://github.com/OpenZeppelin/openzeppelin-contracts
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H- Debilidad (CWE)
CWE-125- Plataforma
- npm
- Paquete
@openzeppelin/contracts, @openzeppelin/contracts-upgradeable- Publicada
- 29.02.2024
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-9vx6-7xxf-x967 - 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
-
OpenZeppelin Contracts base64 encoding may read from potentially dirty memory 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.