Base64 output corruption via out-of-bounds memory read
Published Feb 29, 2024 · Updated Aug 2, 2024
Out-of-bounds reads in OpenZeppelin Contracts 4.5.0 through 4.9.5 and 5.0.0-rc.0 through 5.0.1 allow attackers to corrupt Base64 output. Base64.encode loads three-byte chunks past a nonaligned input buffer, allowing up to four dirty adjacent-memory bits to survive output padding. Reachability requires an input whose length is not a multiple of three and nonzero memory immediately beyond it; the documented consequence is corrupted encoded data.
Summary
What happened
Out-of-bounds reads in OpenZeppelin Contracts 4.5.0 through 4.9.5 and 5.0.0-rc.0 through 5.0.1 allow attackers to corrupt Base64 output. Base64.encode loads three-byte chunks past a nonaligned input buffer, allowing up to four dirty adjacent-memory bits to survive output padding. Reachability requires an input whose length is not a multiple of three and nonzero memory immediately beyond it; the documented consequence is corrupted encoded data.
The record
- CVE
- CVE-2024-27094
- Published
- Feb 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- OpenZeppelin
- Product
- OpenZeppelin Contracts
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.5.0, < 4.9.6
- Affected versionversion=>= 5.0.0-rc.0, < 5.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo