St
29 vulnerabilities.
All published vulnerabilities with a CVE number in St products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2024-50597 | St X-cube-azrt-h7rs: An integer underflow vulnerability exists in the HTTP server PUT request functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 4.3 |
| CVE-2024-50596 | St X-cube-azrt-h7rs: An integer underflow vulnerability exists in the HTTP server PUT request functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 4.3 |
| CVE-2024-50595 | St X-cube-azrt-h7rs: An integer underflow vulnerability exists in the HTTP server PUT request functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 4.3 |
| CVE-2024-50594 | St X-cube-azrt-h7rs: An integer underflow vulnerability exists in the HTTP server PUT request functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 4.3 |
| CVE-2024-50385 | St X-cube-azrt-h7rs: A denial of service vulnerability exists in the NetX Component HTTP server functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 6.5 |
| CVE-2024-50384 | St X-cube-azrt-h7rs: A denial of service vulnerability exists in the NetX Component HTTP server functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 6.5 |
| CVE-2024-45064 | St X-cube-azrt-h7rs: A buffer overflow vulnerability exists in the FileX Internal RAM interface functionality of STMicroelectronics X-CUBE-AZRTOS-WL 2.0.0. A specially … | 2025-04-02 | 8.5 |
| CVE-2023-50096 | St X-cube-safea1: STMicroelectronics STSAFE-A1xx middleware before 3.3.7 allows MCU code execution if an adversary has the ability to read from and write to the I2C … | 2024-01-01 | 7.5 |
| CVE-2023-36629 | St54-android-packages-apps-nfc: The ST ST54-android-packages-apps-Nfc package before 130-20230215-23W07p0 for Android has an out-of-bounds read. | 2024-01-09 | 5.5 |
| CVE-2021-43393 | Stsafe-j Firmware: STMicroelectronics STSAFE-J 1.1.4, J-SAFE3 1.2.5, and J-SIGN sometimes allow attackers to abuse signature verification. This is associated with the … | 2022-03-04 | 6.2 |
| CVE-2021-43392 | St J-safe3 Firmware: STMicroelectronics STSAFE-J 1.1.4, J-SAFE3 1.2.5, and J-SIGN sometimes allow attackers to obtain information on cryptographic secrets. This is … | 2022-03-04 | 6.2 |
| CVE-2021-42553 | Stm32 Mw Usb Host: A buffer overflow vulnerability in stm32_mw_usb_host of STMicroelectronics in versions before 3.5.1 allows an attacker to execute arbitrary code … | 2022-10-21 | 6.8 |
| CVE-2021-34268 | Stm32cube Middleware: An issue in the USBH_ParseDevDesc() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below causes a denial of service (DOS) via a … | 2021-07-22 | 4.6 |
| CVE-2021-34267 | Stm32cube Middleware: An in the USBH_MSC_InterfaceInit() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below causes a denial of service (DOS) when the … | 2021-07-22 | 4.6 |
| CVE-2021-34262 | Stm32cube Middleware: A buffer overflow vulnerability in the USBH_ParseEPDesc() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below allows attackers to … | 2021-07-22 | 6.8 |
| CVE-2021-34261 | Stm32cube Middleware: An issue in USBH_ParseCfgDesc() of STMicroelectronics STM32Cube Middleware v1.8.0 and below causes a denial of service due to the system hanging … | 2021-07-22 | 4.6 |
| CVE-2021-34260 | Stm32cube Middleware: A buffer overflow vulnerability in the USBH_ParseInterfaceDesc() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below allows … | 2021-07-22 | 6.8 |
| CVE-2021-34259 | Stm32cube Middleware: A buffer overflow vulnerability in the USBH_ParseCfgDesc() function of STMicroelectronics STM32Cube Middleware v1.8.0 and below allows attackers to … | 2021-07-22 | 6.8 |
| CVE-2021-29414 | Stm32cubel4 Firmware: STMicroelectronics STM32L4 devices through 2021-03-29 have incorrect physical access control. | 2021-05-21 | 6.1 |
| CVE-2020-27212 | Stm32cubel4 Firmware: STMicroelectronics STM32L4 devices through 2020-10-19 have incorrect access control. The flash read-out protection (RDP) can be degraded from RDP … | 2021-05-21 | 7.0 |
| CVE-2020-20949 | Stm32cubef0: Bleichenbacher's attack on PKCS #1 v1.5 padding for RSA in STM32 cryptographic firmware library software expansion for STM32Cube (UM1924). The … | 2021-01-20 | 5.9 |
| CVE-2020-13466 | Stm32f103 Firmware: STMicroelectronics STM32F103 devices through 2020-05-20 allow physical attackers to execute arbitrary code via a power glitch and a specific flash … | 2020-08-31 | 6.8 |
| CVE-2020-8004 | Stm32f1 Firmware: STMicroelectronics STM32F1 devices have Incorrect Access Control. | 2020-04-06 | 7.5 |
| CVE-2019-19192 | St Wb55: The Bluetooth Low Energy implementation on STMicroelectronics BLE Stack through 1.3.1 for STM32WB5x devices does not properly handle consecutive … | 2020-02-12 | 6.5 |
| CVE-2019-16863 | St33tphf2espi Firmware: STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack … | 2019-11-14 | 5.9 |
| CVE-2019-14238 | Stm32l0 Firmware: On STMicroelectronics STM32F7 devices, Proprietary Code Read Out Protection (PCROP) (a software IP protection method) can be defeated with a debug … | 2019-09-24 | 6.6 |
| CVE-2019-14236 | Stm32l0 Firmware: On STMicroelectronics STM32L0, STM32L1, STM32L4, STM32F4, STM32F7, and STM32H7 devices, Proprietary Code Read Out Protection (PCROP) (a software IP … | 2019-09-12 | 9.8 |
| CVE-2017-18347 | Stm32f071rb Firmware: Incorrect access control in RDP Level 1 on STMicroelectronics STM32F0 series devices allows physically present attackers to extract the device's … | 2018-09-12 | 4.6 |
| CVE-2003-0392 | St Ftp Service: Directory traversal vulnerability in ST FTP Service 3.0 allows remote attackers to list arbitrary directories via a CD command with a DoS drive … | 2003-07-02 | 6.4 |
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.