NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2024-27094: OpenZeppelin Contracts base64 encoding may read from potentially dirty memory

mediumCVSS 3.1 6.5GHSA-9vx6-7xxf-x967

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.

Published Feb 29, 2024 · Updated Mar 14, 2026

Affected packages

@openzeppelin/contracts

Ecosystem
npm
Affected
>= 4.5.0, < 4.9.6
Fixed in
4.9.6
Check
npm ls @openzeppelin/contracts

@openzeppelin/contracts-upgradeable

Ecosystem
npm
Affected
>= 5.0.0-rc.0, < 5.0.2
Fixed in
5.0.2
Check
npm ls @openzeppelin/contracts-upgradeable

@openzeppelin/contracts

Ecosystem
npm
Affected
>= 5.0.0-rc.0, < 5.0.2
Fixed in
5.0.2
Check
npm ls @openzeppelin/contracts

@openzeppelin/contracts-upgradeable

Ecosystem
npm
Affected
>= 4.5.0, < 4.9.6
Fixed in
4.9.6
Check
npm ls @openzeppelin/contracts-upgradeable

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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 memory struct 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)

Credited to rholterhus.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries