CVE-2019-14874: Null Pointer Dereference
First published: Thu Mar 19 2020(Updated: )
In the __i2b function of the newlib libc library, all versions prior to 3.3.0 (see newlib/libc/stdlib/mprec.c), Balloc is used to allocate a big integer, however no check is performed to verify if the allocation succeeded or not. The access of _ x[0] will trigger a null pointer dereference bug in case of a memory allocation failure.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Newlib Project Newlib | <3.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-14874?
CVE-2019-14874 has a medium severity rating due to its potential to cause null pointer dereference issues.
How do I fix CVE-2019-14874?
To fix CVE-2019-14874, upgrade to Newlib version 3.3.0 or later to ensure proper memory allocation checks.
What systems are affected by CVE-2019-14874?
CVE-2019-14874 affects all versions of Newlib prior to 3.3.0.
What type of vulnerability is CVE-2019-14874?
CVE-2019-14874 is a null pointer dereference vulnerability that occurs due to unverified memory allocation.
Can CVE-2019-14874 lead to exploitation?
While CVE-2019-14874 may lead to application crashes, the potential for full exploitation is limited without specific attack vectors.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- agent/source
- vendor/newlib project
- canonical/newlib project newlib