Incorrect access control in RDP Level 1 on STMicroelectronics STM32F0 series devices allows physically present attackers to extract the devi
Incorrect access control in RDP Level 1 on STMicroelectronics STM32F0 series devices allows physically present attackers to extract the device's protected firmware via a special sequence of Serial Wire Debug (SWD) commands because there is a race condition between full initialization of the SWD interface and the setup of flash protection.
- Published
- Sep 12, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-362
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| st | stm32f071rb firmware | cpe:2.3:o:st:stm32f071rb_firmware |
| st | stm32f071rb | cpe:2.3:h:st:stm32f071rb |
| st | stm32f071v8 firmware | cpe:2.3:o:st:stm32f071v8_firmware |
| st | stm32f071v8 | cpe:2.3:h:st:stm32f071v8 |
| st | stm32f071vb firmware | cpe:2.3:o:st:stm32f071vb_firmware |
| st | stm32f071vb | cpe:2.3:h:st:stm32f071vb |
| st | stm32f072c8 firmware | cpe:2.3:o:st:stm32f072c8_firmware |
| st | stm32f072c8 | cpe:2.3:h:st:stm32f072c8 |
| st | stm32f072cb firmware | cpe:2.3:o:st:stm32f072cb_firmware |
| st | stm32f072cb | cpe:2.3:h:st:stm32f072cb |
| st | stm32f072r8 firmware | cpe:2.3:o:st:stm32f072r8_firmware |
| st | stm32f072r8 | cpe:2.3:h:st:stm32f072r8 |
and 132 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- st stm32f030c6 firmwareall versions
- st stm32f030c8 firmwareall versions
- st stm32f030cc firmwareall versions
- st stm32f030f4 firmwareall versions
- st stm32f030k6 firmwareall versions
- st stm32f030r8 firmwareall versions
- st stm32f030rc firmwareall versions
- st stm32f031c4 firmwareall versions
- st stm32f031c6 firmwareall versions
- st stm32f031e6 firmwareall versions
- st stm32f031f4 firmwareall versions
- st stm32f031f6 firmwareall versions
- st stm32f031g4 firmwareall versions
- st stm32f031g6 firmwareall versions
- st stm32f031k4 firmwareall versions
- st stm32f038c6 firmwareall versions
- st stm32f038e6 firmwareall versions
- st stm32f038f6 firmwareall versions
- st stm32f038g6 firmwareall versions
- st stm32f038k6 firmwareall versions
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.