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

> A privileged local attacker can escalate privileges due to insufficient memory protection in System Management Mode on Intel 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-jh65-fgr7-8269

## What is CVE-2019-0152?

CVE-2019-0152 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 System Management Mode (SMM) and Intel(R) TXT for certain 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-0152?

It affects 130 products.


Products: Intel Xeon Bronze 3104 Firmware, Intel Xeon Bronze 3106 Firmware, Intel Xeon Bronze 3204 Firmware, Intel Xeon D-2123it Firmware, Intel Xeon D-2141i Firmware, Intel Xeon D-2142it Firmware, Intel Xeon D-2143it Firmware, Intel Xeon D-2145nt Firmware, Intel Xeon D-2146nt Firmware, Intel Xeon D-2161i Firmware, Intel Xeon D-2163it Firmware, Intel Xeon D-2166nt Firmware, Intel Xeon D-2173it Firmware, Intel Xeon D-2177nt Firmware, Intel Xeon D-2183it Firmware, Intel Xeon D-2187nt Firmware, Intel Xeon Gold 5115 Firmware, Intel Xeon Gold 5118 Firmware, Intel Xeon Gold 5120 Firmware, Intel Xeon Gold 5120t Firmware and 110 more.

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

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

## Is CVE-2019-0152 being exploited?

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

## Other vulnerabilities in 2019.2 IPU – Intel(R) Processor Security

- [CVE-2022-26343](https://insights.sbomify.com/CVE-2022-26343/): Privilege escalation in Intel(R) Processors (high 8.2)
- [CVE-2020-0590](https://insights.sbomify.com/CVE-2020-0590/): Privilege escalation in Intel(R) Processors (high 7.8)
- [CVE-2022-32231](https://insights.sbomify.com/CVE-2022-32231/): Privilege escalation in Intel(R) Processors (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0152 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-0152 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-0152/ (Markdown: https://insights.sbomify.com/CVE-2019-0152/index.md)
```

## Sources

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

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