Skip to main content
No exploitation reported

CVE-2019-14236

No exploitation reported by the sources we read.

  • Published2019-09-12
  • WeaknessCWE-863

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2019-09-1218:15CVE publishedNVD

Versions per branch

NVD
St stm32f4 firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published
St stm32f7 firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published
St stm32h7 firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published

3 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2019-09-12
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-2h75-rwg4-wvhq

Frequently asked questions

What is CVE-2019-14236?

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.

Is CVE-2019-14236 actively exploited?

Active exploitation of CVE-2019-14236 has not been confirmed. Its EPSS score was 2.3% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-14236?

CVE-2019-14236 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record