CVE-2017-18347
What it is
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.
At a glance
- Exploitability
- Can be exploited with physical access without logging in. High risk of data exposure.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 4.6 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- St stm32f071rb Firmware
- St stm32f071v8 Firmware
- St stm32f071vb Firmware
- St stm32f072c8 Firmware
- St stm32f072cb Firmware
- St stm32f072r8 Firmware
- St stm32f072rb Firmware
- St stm32f072v8 Firmware
Attack profile CVSS 3.1 · 4.6
- Attack vector
- Physical
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-18347.md and follow it. Check whether this project is affected by CVE-2017-18347. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://community.st.com/s/question/0D50X00009Xke7aSAB/readout-protection-cracked-on-stm32
- https://community.st.com/s/question/0D50X00009Xke7aSAB/readout-protection-cracked-on-stm32
References
- https://community.st.com/s/question/0D50X00009Xke7aSAB/readout-protection-cracked-on-stm32
- https://www.aisec.fraunhofer.de/en/FirmwareProtection.html
- https://www.usenix.org/conference/woot17/workshop-program/presentation/obermaier
- https://community.st.com/s/question/0D50X00009Xke7aSAB/readout-protection-cracked-on-stm32
- https://www.aisec.fraunhofer.de/en/FirmwareProtection.html
- https://www.usenix.org/conference/woot17/workshop-program/presentation/obermaier