# CVE-2020-8675: Privilege escalation in Intel(R)Innovation Engine Advisory

> An unauthenticated attacker with physical access can escalate privileges via insufficient control flow management in the Intel Innovation Engine firmware build tool.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6fwj-c62c-xvxm

## What is CVE-2020-8675?

CVE-2020-8675 is a medium-severity vulnerability in Intel(R)Innovation Engine Advisory, published on 15 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient control flow management in firmware build and signing tool for Intel(R) Innovation Engine before version 1.0.859 may allow an unauthenticated user to potentially enable escalation of privilege via physical access.

## Which versions are affected by CVE-2020-8675?

It affects 1 product.


Products: Intel Innovation Engine Firmware.

## How do I fix CVE-2020-8675?

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

## Is CVE-2020-8675 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8675 and fix it if it is affected.

What it is: CVE-2020-8675 is a medium-severity vulnerability in Intel(R)Innovation Engine Advisory, published on 15 Jun 2020. 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-2020-8675 in the wild and no public exploit code.

Affected product: Intel(R)Innovation Engine Advisory. 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-2020-8675/ (Markdown: https://insights.sbomify.com/CVE-2020-8675/index.md)
```

## Sources

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

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