# CVE-2019-0151: Privilege escalation in 2019.2 IPU – Intel(R) Processor Security

> A privileged local attacker can escalate privileges due to insufficient memory protection in Intel TXT on certain Core and Xeon processors.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/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:** 14 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p4x6-pmx2-w6pr

## What is CVE-2019-0151?

CVE-2019-0151 is a medium-severity vulnerability in 2019.2 IPU – Intel(R) Processor Security, 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 memory protection in Intel(R) TXT for certain Intel(R) Core Processors and Intel(R) Xeon(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 444 products.


Products: Intel Core I5-5300u Firmware, Intel Core I5-5350u Firmware, Intel Core I5-6300u Firmware, Intel Core I5-6360u Firmware, Intel Core I5-6440hq Firmware, Intel Core I5-6500 Firmware, Intel Core I5-7300u Firmware, Intel Core I5-7y57 Firmware, Intel Core I5-8350u Firmware, Intel Core I5-8365u Firmware, Intel Core I5-8400h Firmware, Intel Core I5-8500 Firmware, Intel Core I5-8500t Firmware, Intel Core I5-8600 Firmware, Intel Core I5-8600k Firmware, Intel Core I5-8600t Firmware, Intel Core I5-9400h Firmware, Intel Core I5-9500 Firmware, Intel Core I5-9500t Firmware, Intel Core I5-9600 Firmware and 424 more.

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

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

## Is CVE-2019-0151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0151 is a medium-severity vulnerability in 2019.2 IPU – Intel(R) Processor Security, 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-0151 in the wild and no public exploit code.

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

## Sources

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

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