# CVE-2019-11157: Privilege escalation in Intel(R) Processors

> A privileged local attacker can exploit improper voltage condition checks in Intel processors to escalate privileges or disclose information.

- **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:** Yes
- **Published:** 16 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r3vh-cpmh-5vhc, UBUNTU-CVE-2019-11157

## What is CVE-2019-11157?

CVE-2019-11157 is a medium-severity vulnerability in Intel(R) Processors, published on 16 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper conditions check in voltage settings for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege and/or information disclosure via local access.

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

It affects 264 products.


Products: Intel Core I3-1000g1 Firmware, Intel Core I3-1000g4 Firmware, Intel Core I3-1005g1 Firmware, Intel Core I3-10110u Firmware, Intel Core I3-10110y Firmware, Intel Core I3-6006u Firmware, Intel Core I3-6098p Firmware, Intel Core I3-6100 Firmware, Intel Core I3-6100e Firmware, Intel Core I3-6100h Firmware, Intel Core I3-6100t Firmware, Intel Core I3-6100te Firmware, Intel Core I3-6100u Firmware, Intel Core I3-6102e Firmware, Intel Core I3-6157u Firmware, Intel Core I3-6167u Firmware, Intel Core I3-6300 Firmware, Intel Core I3-6300t Firmware, Intel Core I3-6320 Firmware, Intel Core I3-7020u Firmware and 244 more.

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

Apply the vendor's patch.

## Is CVE-2019-11157 being exploited?

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

Public exploit code:

- Tool Suite for V0LTpwn (CVE-2019-11157). Code will be published soon. (github_poc): https://github.com/zkenjar/v0ltpwn

## Other vulnerabilities in Intel(R) Processors

- [CVE-2021-33123](https://insights.sbomify.com/CVE-2021-33123/): Privilege escalation in Intel(R) Processors (high 7.8)
- [CVE-2022-33894](https://insights.sbomify.com/CVE-2022-33894/): Privilege escalation in Intel(R) Processors (high 7.5)
- [CVE-2021-33103](https://insights.sbomify.com/CVE-2021-33103/): Privilege escalation in Intel(R) Processors (medium 6.7)
- [CVE-2021-33124](https://insights.sbomify.com/CVE-2021-33124/): Memory corruption in Intel(R) Processors (medium 6.7)
- [CVE-2019-14607](https://insights.sbomify.com/CVE-2019-14607/): Privilege escalation in Intel® Processors (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11157 is a medium-severity vulnerability in Intel(R) Processors, published on 16 Dec 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-11157 in the wild and no public exploit code.

Affected product: Intel(R) Processors. 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-11157/ (Markdown: https://insights.sbomify.com/CVE-2019-11157/index.md)
```

## Sources

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

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