Nxp
18 vulnerabilities.
All published vulnerabilities with a CVE number in Nxp products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2023-39902 | Nxp Uboot Secondary Program Loader: A software vulnerability has been identified in the U-Boot Secondary Program Loader (SPL) before 2023.07 on select NXP i.MX 8M family processors. … | 2023-10-17 | 7.0 |
| CVE-2022-45163 | Nxp I.mx 6 Firmware: An information-disclosure vulnerability exists on select NXP devices when configured in Serial Download Protocol (SDP) mode: i.MX RT 1010, i.MX RT … | 2022-11-18 | 5.3 |
| CVE-2022-22819 | Nxp Lpc55s66jbd64 Firmware: NXP LPC55S66JBD64, LPC55S66JBD100, LPC55S66JEV98, LPC55S69JBD64, LPC55S69JBD100, and LPC55S69JEV98 microcontrollers (ROM version 1B) have a buffer … | 2022-03-23 | 7.8 |
| CVE-2021-44479 | Nxp Kinetis K82 Firmware: NXP Kinetis K82 devices have a buffer over-read via a crafted wlength value in a GET Status-Other request during use of USB In-System Programming … | 2021-12-01 | 6.1 |
| CVE-2021-40154 | Nxp Lpc55s69jbd100 Firmware: NXP LPC55S69 devices before A3 have a buffer over-read via a crafted wlength value in a GET Descriptor Configuration request during use of USB … | 2021-12-01 | 6.1 |
| CVE-2021-38260 | Nxp Mcuxpresso Software Development Kit: NXP MCUXpresso SDK v2.7.0 was discovered to contain a buffer overflow in the function USB_HostParseDeviceConfigurationDescriptor(). | 2021-10-25 | 7.8 |
| CVE-2021-38258 | Nxp Mcuxpresso Software Development Kit: NXP MCUXpresso SDK v2.7.0 was discovered to contain a buffer overflow in the function USB_HostProcessCallback(). | 2021-10-25 | 7.8 |
| CVE-2021-33881 | Nxp Mifare Ultralight Ev1 Firmware: On NXP MIFARE Ultralight and NTAG cards, an attacker can interrupt a write operation (aka conduct a "tear off" attack) over RFID to bypass a … | 2021-06-06 | 4.2 |
| CVE-2021-31532 | Nxp Lpc55s69jbd100 Firmware: NXP LPC55S6x microcontrollers (0A and 1B), i.MX RT500 (silicon rev B1 and B2), i.MX RT600 (silicon rev A0, B0), LPC55S6x, LPC55S2x, LPC552x … | 2021-05-06 | 6.8 |
| CVE-2021-27421 | Nxp Mcuxpresso Software Development Kit: NXP MCUXpresso SDK versions prior to 2.8.2 are vulnerable to integer overflow in SDK_Malloc function, which could allow to access memory locations … | 2022-05-03 | 7.3 |
| CVE-2021-22680 | Nxp Mqx: NXP MQX Versions 5.1 and prior are vulnerable to integer overflow in mem_alloc, _lwmem_alloc and _partition functions. This unverified memory … | 2022-05-03 | 7.3 |
| CVE-2021-3011 | Ftsafe K13: An electromagnetic-wave side-channel issue was discovered on NXP SmartMX / P5x security microcontrollers and A7x secure authentication … | 2021-01-07 | 4.2 |
| CVE-2019-17519 | Nxp Mcuxpresso Software Development Kit: The Bluetooth Low Energy implementation on NXP SDK through 2.2.1 for KW41Z devices does not properly restrict the Link Layer payload length, … | 2020-02-12 | 8.8 |
| CVE-2019-17060 | Nxp Mcuxpresso Software Development Kit: The Bluetooth Low Energy (BLE) stack implementation on the NXP KW41Z (based on the MCUXpresso SDK with Bluetooth Low Energy Driver 2.2.1 and … | 2020-02-10 | 6.5 |
| CVE-2019-14239 | Nxp Kinetis Kv1x Firmware: On NXP Kinetis KV1x, Kinetis KV3x, and Kinetis K8x devices, Flash Access Controls (FAC) (a software IP protection method for execute-only access) … | 2019-09-24 | 6.6 |
| CVE-2019-14237 | Nxp Kinetis Kv1x Firmware: On NXP Kinetis KV1x, Kinetis KV3x, and Kinetis K8x devices, Flash Access Controls (FAC) (a software IP protection method for execute-only access) … | 2019-09-12 | 9.8 |
| CVE-2017-7936 | Nxp Vybrid Mvf30nn151cku26 Firmware: A stack-based buffer overflow issue was discovered in NXP i.MX 50, i.MX 53, i.MX 6ULL, i.MX 6UltraLite, i.MX 6SoloLite, i.MX 6Solo, i.MX 6DualLite, … | 2017-08-07 | 6.3 |
| CVE-2017-7932 | Nxp Vybrid Mvf30nn151cku26 Firmware: An improper certificate validation issue was discovered in NXP i.MX 28 i.MX 50, i.MX 53, i.MX 7Solo i.MX 7Dual Vybrid VF3xx, Vybrid VF5xx, Vybrid … | 2017-08-07 | 6.0 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.