First published: Tue Sep 24 2019(Updated: )
On STMicroelectronics STM32F7 devices, Proprietary Code Read Out Protection (PCROP) (a software IP protection method) can be defeated with a debug probe via the Instruction Tightly Coupled Memory (ITCM) bus.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
St Stm32l0 Firmware | ||
St Stm32l0 | ||
St Stm32l1 Firmware | ||
St Stm32l1 | ||
St Stm32f4 Firmware | ||
St Stm32f4 | ||
St Stm32l4 Firmware | ||
St Stm32l4 | ||
St Stm32f7 Firmware | ||
St Stm32f7 | ||
St Stm32h7 Firmware | ||
St Stm32h7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2019-14238.
The severity of CVE-2019-14238 is medium.
Proprietary Code Read Out Protection (PCROP) on STMicroelectronics STM32F7 devices can be defeated with a debug probe via the Instruction Tightly Coupled Memory (ITCM) bus.
The affected software for CVE-2019-14238 includes STMicroelectronics STM32L0 Firmware, STMicroelectronics STM32L1 Firmware, STMicroelectronics STM32F4 Firmware, STMicroelectronics STM32L4 Firmware, STMicroelectronics STM32F7 Firmware, and STMicroelectronics STM32H7 Firmware.
No, STMicroelectronics STM32L0, STM32L1, STM32F4, STM32L4, STM32F7, and STM32H7 are not vulnerable to CVE-2019-14238.
Yes, you can refer to the following links for more information on CVE-2019-14238: [Whitepaper 1](https://www.usenix.org/conference/woot19/presentation/schink) and [Whitepaper 2](https://www.usenix.org/system/files/woot19-paper_schink.pdf).
The Common Weakness Enumeration (CWE) for CVE-2019-14238 is CWE-287.