# CVE-2017-5710: Privilege escalation in Trusted Execution Engine

> An unauthorized process can escalate privileges and access privileged content in Intel Trusted Execution Engine Firmware.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gh27-fc47-858c

## What is CVE-2017-5710?

CVE-2017-5710 is a high-severity vulnerability in Intel Corporation Trusted Execution Engine, published on 21 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple privilege escalations in kernel in Intel Trusted Execution Engine Firmware 3.0 allows unauthorized process to access privileged content via unspecified vector.

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

It affects 1 product.


Products: Intel Trusted Execution Engine Firmware.

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

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

## Is CVE-2017-5710 being exploited?

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

## Other vulnerabilities in Intel Corporation Trusted Execution Engine

- [CVE-2019-11097](https://insights.sbomify.com/CVE-2019-11097/): Privilege escalation in Intel(R) Management Engine (high 7.8)
- [CVE-2017-5707](https://insights.sbomify.com/CVE-2017-5707/): Memory corruption in Trusted Execution Engine (high 7.8)
- [CVE-2020-0566](https://insights.sbomify.com/CVE-2020-0566/): Privilege escalation in Intel(R) TXE (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5710 is a high-severity vulnerability in Intel Corporation Trusted Execution Engine, published on 21 Nov 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-5710 in the wild and no public exploit code.

Affected product: Intel Corporation Trusted Execution Engine. 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-5710/ (Markdown: https://insights.sbomify.com/CVE-2017-5710/index.md)
```

## Sources

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

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