# CVE-2017-5703: Privilege escalation in Intel 6th generation Intel Core Processors, Intel 7th generation Processors, Intel Xeon Scalable Processors, Intel Xeon Processor E3 v5 Family, Intel Xeon Processor E3 v6 Family, and Intel Atom Processor C Series.

> A local attacker can alter SPI flash behavior on Intel platforms, potentially causing denial of service or privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rwvg-wfj8-f23j

## What is CVE-2017-5703?

CVE-2017-5703 is a medium-severity vulnerability in Intel 6th generation Intel Core Processors, Intel 7th generation Processors, Intel Xeon Scalable Processors, Intel Xeon Processor E3 v5 Family, Intel Xeon Processor E3 v6 Family, and Intel Atom Processor C Series., published on 3 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Configuration of SPI Flash in platforms based on multiple Intel platforms allow a local attacker to alter the behavior of the SPI flash potentially leading to a Denial of Service.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 308 products.


Products: Intel Atom C2308, Intel Atom C2316, Intel Atom C2338, Intel Atom C2350, Intel Atom C2358, Intel Atom C2508, Intel Atom C2516, Intel Atom C2518, Intel Atom C2530, Intel Atom C2538, Intel Atom C2550, Intel Atom C2558, Intel Atom C2718, Intel Atom C2730, Intel Atom C2738, Intel Atom C2750, Intel Atom C2758, Intel Atom C3308, Intel Atom C3338, Intel Atom C3508 and 288 more.

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

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

## Is CVE-2017-5703 being exploited?

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

## Other vulnerabilities in Intel 6th generation Intel Core Processors, Intel 7th generation Processors, Intel Xeon Scalable Processors, Intel Xeon Processor E3 v5 Family, Intel Xeon Processor E3 v6 Family, and Intel Atom Processor C Series.

- [CVE-2021-33150](https://insights.sbomify.com/CVE-2021-33150/): Privilege escalation in Intel(R) Trace Hub instances which (medium 6.8)
- [CVE-2020-0551](https://insights.sbomify.com/CVE-2020-0551/): Information disclosure in Intel(R) Processors Load Value Injection (medium 5.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5703 is a medium-severity vulnerability in Intel 6th generation Intel Core Processors, Intel 7th generation Processors, Intel Xeon Scalable Processors, Intel Xeon Processor E3 v5 Family, Intel Xeon Processor E3 v6 Family, and Intel Atom Processor C Series., published on 3 Apr 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-5703 in the wild and no public exploit code.

Affected product: Intel 6th generation Intel Core Processors, Intel 7th generation Processors, Intel Xeon Scalable Processors, Intel Xeon Processor E3 v5 Family, Intel Xeon Processor E3 v6 Family, and Intel Atom Processor C Series.. 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-5703/ (Markdown: https://insights.sbomify.com/CVE-2017-5703/index.md)
```

## Sources

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

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