Heap buffer overflow via allocation-size integer wraparound
Published Mar 5, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Newlib Project Newlib before 4.0.0 allows attackers to corrupt memory via oversized allocation requests. mEMALIGn checks a size_t request against INT_MAX and fails to reserve space for alignment, while pvALLOc and nano variants omit equivalent bounds checks before rounding or padding the request. An application must pass an attacker-controlled size to an affected API; the resulting overwrite is bounded by that application's privileges and platform.
Summary
What happened
Heap-based buffer overflow in Newlib Project Newlib before 4.0.0 allows attackers to corrupt memory via oversized allocation requests. mEMALIGn checks a size_t request against INT_MAX and fails to reserve space for alignment, while pvALLOc and nano variants omit equivalent bounds checks before rounding or padding the request. An application must pass an attacker-controlled size to an affected API; the resulting overwrite is bounded by that application's privileges and platform.
The record
- CVE
- CVE-2021-3420
- Published
- Mar 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Newlib Project
- Product
- Newlib
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=newlib versions prior to 4.0.0
What conditions does exploitation require?
What is affected?
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