# CVE-2017-18347: Race condition in n/a

> Physically present attackers can extract protected firmware from STM32F0 devices by exploiting a race condition during SWD interface initialization.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5f4r-g29m-jw8q

## What is CVE-2017-18347?

CVE-2017-18347 is a medium-severity vulnerability in n/a, published on 12 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2017-18347?

It affects 72 products.


Products: St Stm32f030c6 Firmware, St Stm32f030c8 Firmware, St Stm32f030cc Firmware, St Stm32f030f4 Firmware, St Stm32f030k6 Firmware, St Stm32f030r8 Firmware, St Stm32f030rc Firmware, St Stm32f031c4 Firmware, St Stm32f031c6 Firmware, St Stm32f031e6 Firmware, St Stm32f031f4 Firmware, St Stm32f031f6 Firmware, St Stm32f031g4 Firmware, St Stm32f031g6 Firmware, St Stm32f031k4 Firmware, St Stm32f038c6 Firmware, St Stm32f038e6 Firmware, St Stm32f038f6 Firmware, St Stm32f038g6 Firmware, St Stm32f038k6 Firmware and 52 more.

## How do I fix CVE-2017-18347?

No fix has been published for CVE-2017-18347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-18347 being exploited?

There is no known exploitation of CVE-2017-18347 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18347 and fix it if it is affected.

What it is: CVE-2017-18347 is a medium-severity vulnerability in n/a, published on 12 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18347 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18347/ (Markdown: https://insights.sbomify.com/CVE-2017-18347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18347
- OSV: https://osv.dev/vulnerability/CVE-2017-18347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18347/
Summaries are generated and may contain mistakes; the official description above is the record.