Crash via unchecked big-integer allocation result
Published Mar 19, 2020 · Updated Aug 5, 2024
NULL pointer dereference in Newlib before 3.3.0 allows attackers to crash embedded software under low-memory conditions. The __multiply function uses Balloc to create a big integer but dereferences the returned _x member without checking whether allocation returned NULL. Triggering requires a consuming firmware path that invokes __multiply after allocation failure; the resulting dereference can halt that software.
Summary
What happened
NULL pointer dereference in Newlib before 3.3.0 allows attackers to crash embedded software under low-memory conditions. The __multiply function uses Balloc to create a big integer but dereferences the returned _x member without checking whether allocation returned NULL. Triggering requires a consuming firmware path that invokes __multiply after allocation failure; the resulting dereference can halt that software.
The record
- CVE
- CVE-2019-14875
- Published
- Mar 19, 2020
- Updated
- Aug 5, 2024
- Vendor
- Newlib Project
- Product
- Newlib
- Classifications
- CWE-476, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=all newlib versions prior to 3.3.0
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