# CVE-2017-5685: Information disclosure in Intel NUC NUC6i7KYK

> An attacker with physical access can exploit a BIOS vulnerability in Intel NUC systems to access personal information.

- **Severity:** Low 3.9 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **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 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5rwh-cqfm-wv9v

## What is CVE-2017-5685?

CVE-2017-5685 is a low-severity vulnerability in Intel NUC NUC6i7KYK, published on 3 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The BIOS in Intel NUC systems based on 6th Gen Intel Core processors prior to version KY0045 may allow may allow an attacker with physical access to the system to gain access to personal information.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Intel Nuc6i7kyk Bios.

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

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

## Is CVE-2017-5685 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5685 is a low-severity vulnerability in Intel NUC NUC6i7KYK, published on 3 Apr 2017. 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-5685 in the wild and no public exploit code.

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

## Sources

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

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