# CVE-2019-0117: Information disclosure in 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update

> A privileged local attacker can exploit insufficient access control in Intel SGX to disclose protected memory information.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/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:** Yes
- **Published:** 14 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hg94-7qqv-5v36, RHEA-2019:3846, RHEA-2019:3847, RHEA-2019:3848, RHEA-2019:3849, RHEA-2019:3850, RHEA-2019:3851, RHEA-2019:3852, RHEA-2019:3853, RHEA-2019:3854

## What is CVE-2019-0117?

CVE-2019-0117 is a medium-severity vulnerability in 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update, published on 14 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient access control in protected memory subsystem for Intel(R) SGX for 6th, 7th, 8th, 9th Generation Intel(R) Core(TM) Processor Families; Intel(R) Xeon(R) Processor E3-1500 v5, v6 Families; Intel(R) Xeon(R) E-2100 & E-2200 Processor Families with Intel(R) Processor Graphics may allow a privileged user to potentially enable information disclosure via local access.

## Which versions are affected by CVE-2019-0117?

It affects 163 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `microcode_ctl` | Red Hat:enterprise_linux:6::client | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl` | Red Hat:enterprise_linux:6::server | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 2:1.17-33.19.el6_10 |
| `microcode_ctl` | Red Hat:enterprise_linux:7::client | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl` | Red Hat:enterprise_linux:7::computenode | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl` | Red Hat:enterprise_linux:7::server | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl` | Red Hat:enterprise_linux:7::workstation | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 2:2.1-53.3.el7_7 |
| `microcode_ctl` | Red Hat:rhel_aus:6.5::server | All versions | 2:1.17-17.25.el6_5 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_aus:6.5::server | All versions | 2:1.17-17.25.el6_5 |
| `microcode_ctl` | Red Hat:rhel_aus:6.6::server | All versions | 2:1.17-19.23.el6_6 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_aus:6.6::server | All versions | 2:1.17-19.23.el6_6 |
| `microcode_ctl` | Red Hat:rhel_aus:7.2::server | All versions | 2:2.1-12.24.el7_2 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_aus:7.2::server | All versions | 2:2.1-12.24.el7_2 |
| `microcode_ctl` | Red Hat:rhel_aus:7.3::server | All versions | 2:2.1-16.27.el7_3 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_aus:7.3::server | All versions | 2:2.1-16.27.el7_3 |
| `microcode_ctl` | Red Hat:rhel_aus:7.4::server | All versions | 2:2.1-22.26.el7_4 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 2:2.1-22.26.el7_4 |
| `microcode_ctl` | Red Hat:rhel_e4s:7.2::server | All versions | 2:2.1-12.24.el7_2 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_e4s:7.2::server | All versions | 2:2.1-12.24.el7_2 |
| `microcode_ctl` | Red Hat:rhel_e4s:7.3::server | All versions | 2:2.1-16.27.el7_3 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_e4s:7.3::server | All versions | 2:2.1-16.27.el7_3 |
| `microcode_ctl` | Red Hat:rhel_e4s:7.4::server | All versions | 2:2.1-22.26.el7_4 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_e4s:7.4::server | All versions | 2:2.1-22.26.el7_4 |
| `microcode_ctl` | Red Hat:rhel_eus:7.5::computenode | All versions | 2:2.1-29.24.el7_5 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_eus:7.5::computenode | All versions | 2:2.1-29.24.el7_5 |
| `microcode_ctl` | Red Hat:rhel_eus:7.5::server | All versions | 2:2.1-29.24.el7_5 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_eus:7.5::server | All versions | 2:2.1-29.24.el7_5 |
| `microcode_ctl` | Red Hat:rhel_eus:7.6::computenode | All versions | 2:2.1-47.8.el7_6 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_eus:7.6::computenode | All versions | 2:2.1-47.8.el7_6 |
| `microcode_ctl` | Red Hat:rhel_eus:7.6::server | All versions | 2:2.1-47.8.el7_6 |
| `microcode_ctl-debuginfo` | Red Hat:rhel_eus:7.6::server | All versions | 2:2.1-47.8.el7_6 |

Products: Intel Core I5-7200u Firmware, Intel Core I5-7260u Firmware, Intel Core I5-7267u Firmware, Intel Core I5-7287u Firmware, Intel Core I5-7300hq Firmware, Intel Core I5-7300u Firmware, Intel Core I5-7360u Firmware, Intel Core I5-7400 Firmware, Intel Core I5-7400t Firmware, Intel Core I5-7440eq Firmware, Intel Core I5-7440hq Firmware, Intel Core I5-7442eq Firmware, Intel Core I5-7500 Firmware, Intel Core I5-7500t Firmware, Intel Core I5-7600 Firmware, Intel Core I5-7600k Firmware, Intel Core I5-7600t Firmware, Intel Core I5-7y54 Firmware, Intel Core I5-7y57 Firmware, Intel Core I7-6500u Firmware and 143 more.

## How do I fix CVE-2019-0117?

Apply the vendor's patch.

## Is CVE-2019-0117 being exploited?

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

## Other vulnerabilities in 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update

- [CVE-2020-0528](https://insights.sbomify.com/CVE-2020-0528/): Memory corruption in BIOS (high 7.8)
- [CVE-2020-0529](https://insights.sbomify.com/CVE-2020-0529/): Privilege escalation in BIOS (high 7.8)
- [CVE-2019-0185](https://insights.sbomify.com/CVE-2019-0185/): Information disclosure in 2019.2 IPU – Intel(R) Processor Graphics SMM (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0117 and fix it if it is affected.

What it is: CVE-2019-0117 is a medium-severity vulnerability in 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update, published on 14 Nov 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-2019-0117 in the wild and no public exploit code.

Affected product: 2019.2 IPU – Intel(R) SGX with Intel(R) Processor Graphics Update. 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-2019-0117/ (Markdown: https://insights.sbomify.com/CVE-2019-0117/index.md)
```

## Sources

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

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