This page lists publicly disclosed CVE vulnerabilities affecting newlib_project newlib (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2024-30949 | An issue in newlib v.4.3.0 allows an attacker to execute arbitrary code via the time unit scaling in the _gettimeofday function. | [email protected] | 9.8 | 0.69% | 2024-08-20 | 2024-08-21 |
| CVE-2021-3420 | A flaw was found in newlib in versions prior to 4.0.0. Improper overflow validation in the memory allocation functions mEMALIGn, pvALLOc, nano_memalign, nano_valloc, nano_pvalloc could case an integer overflow, leading to an allocation of a small buffer and then to a heap-based buffer overflow. | [email protected] | 9.8 | 0.14% | 2021-03-05 | 2024-11-21 |
| CVE-2019-14878 | In the __d2b 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. Accessing _x will trigger a null pointer dereference bug in case of a memory allocation failure. | [email protected] | 6.5 | 0.31% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14877 | In the __mdiff function of the newlib libc library, all versions prior to 3.3.0 (see newlib/libc/stdlib/mprec.c), Balloc is used to allocate big integers, however no check is performed to verify if the allocation succeeded or not. The access to _wds and _sign will trigger a null pointer dereference bug in case of a memory allocation failure. | [email protected] | 6.5 | 0.31% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14876 | 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. | [email protected] | 6.5 | 0.40% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14875 | In the __multiply 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. | [email protected] | 6.5 | 0.40% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14874 | 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. | [email protected] | 6.5 | 0.40% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14873 | In the __multadd function of the newlib libc library, prior to versions 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. This will trigger a null pointer dereference bug in case of a memory allocation failure. | [email protected] | 6.5 | 0.40% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14872 | The _dtoa_r function of the newlib libc library, prior to version 3.3.0, performs multiple memory allocations without checking their return value. This could result in NULL pointer dereference. | [email protected] | 6.5 | 0.41% | 2020-03-19 | 2024-11-21 |
| CVE-2019-14871 | The REENT_CHECK macro (see newlib/libc/include/sys/reent.h) as used by REENT_CHECK_TM, REENT_CHECK_MISC, REENT_CHECK_MP and other newlib macros in versions prior to 3.3.0, does not check for memory allocation problems when the DEBUG flag is unset (as is the case in production firmware builds). | [email protected] | 6.5 | 0.46% | 2020-03-18 | 2024-11-21 |