CVE-2019-14876: Null Pointer Dereference
First published: Thu Mar 19 2020(Updated: )
In the __lshift 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 to b1 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-14876?
CVE-2019-14876 is categorized as a medium severity vulnerability due to potential null pointer dereference issues.
How do I fix CVE-2019-14876?
To mitigate CVE-2019-14876, upgrade Newlib to version 3.3.0 or later, where the allocation check is properly implemented.
What systems are affected by CVE-2019-14876?
CVE-2019-14876 affects all versions of Newlib prior to 3.3.0.
What type of vulnerability is CVE-2019-14876?
CVE-2019-14876 is a null pointer dereference vulnerability within the __lshift function of the Newlib libc library.
Is CVE-2019-14876 exploitable in production environments?
Yes, if an application uses Newlib versions prior to 3.3.0, CVE-2019-14876 may be exploitable, potentially leading to application crashes.
- 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/tags
- agent/event
- agent/source
- vendor/newlib project
- canonical/newlib project newlib