# CVE-2017-3718: Privilege escalation in Intel(R) NUC

> A privileged user with physical access can escalate privileges due to improper device configuration in Intel NUC system firmware.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 10 Jan 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-j49j-9f8j-jjfx

## What is CVE-2017-3718?

CVE-2017-3718 is a medium-severity vulnerability in Intel(R) NUC, published on 10 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper setting of device configuration in system firmware for Intel(R) NUC kits may allow a privileged user to potentially enable escalation of privilege via physical access.

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

It affects 3 products.


Products: Intel Compute Card Firmware, Intel Compute Stick Firmware, Intel Nuc Kit Firmware.

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

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

## Is CVE-2017-3718 being exploited?

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

## Other vulnerabilities in Intel(R) NUC

- [CVE-2018-12176](https://insights.sbomify.com/CVE-2018-12176/): Code injection in Intel(R) NUC Kits and Intel(R) Compute Cards (high 8.2)
- [CVE-2019-11140](https://insights.sbomify.com/CVE-2019-11140/): Privilege escalation in Intel(R) NUC Advisory (medium 6.7)
- [CVE-2019-11123](https://insights.sbomify.com/CVE-2019-11123/): Privilege escalation in Intel(R) NUC Firmware (medium 6.7)
- [CVE-2019-11124](https://insights.sbomify.com/CVE-2019-11124/): Memory corruption in Intel(R) NUC Firmware (medium 6.7)
- [CVE-2019-11125](https://insights.sbomify.com/CVE-2019-11125/): Privilege escalation in Intel(R) NUC Firmware (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3718 is a medium-severity vulnerability in Intel(R) NUC, published on 10 Jan 2019. 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-3718 in the wild and no public exploit code.

Affected product: Intel(R) NUC. 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-3718/ (Markdown: https://insights.sbomify.com/CVE-2017-3718/index.md)
```

## Sources

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

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