@openzeppelin/contracts
Affected
- introduced
4.5.0, fixed4.9.6(semver)
Fixed versions
4.9.6
Fix
- Fixed version
4.9.6npm install @openzeppelin/[email protected]
Advisory
Also known as: CVE-2024-27094
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:
bytes memory struct is allocated just after the input and the first bytes of it are non-zero.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)
Medium Basis: The source's own band: MODERATE
4.5.0, fixed 4.9.6 (semver)4.9.6
4.9.6npm install @openzeppelin/[email protected]5.0.0-rc.0, fixed 5.0.2 (semver)5.0.2
5.0.2npm install @openzeppelin/[email protected]5.0.0-rc.0, fixed 5.0.2 (semver)5.0.2
5.0.2npm install @openzeppelin/[email protected]4.5.0, fixed 4.9.6 (semver)4.9.6
4.9.6npm install @openzeppelin/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0