# CVE-2019-0161: Memory corruption in Extensible Firmware Interface Development Kit (EDK II)

> A stack overflow in EDK II XHCI allows local attackers to cause a denial of service, requiring firmware updates.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** Yes
- **Published:** 27 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-0161, GHSA-jf2h-frpc-5873, SUSE-SU-2019:1110-1, SUSE-SU-2019:1157-1, SUSE-SU-2019:1204-1, UBUNTU-CVE-2019-0161, openSUSE-SU-2019:1352-1

## What is CVE-2019-0161?

CVE-2019-0161 is a medium-severity memory corruption vulnerability in Extensible Firmware Interface Development Kit (EDK II), published on 27 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack overflow in XHCI for EDK II may allow an unauthenticated user to potentially enable denial of service via local access.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ovmf` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 2017+git1510945757.b2662641d5-3.16.1 |
| `ovmf` | SUSE:Linux Enterprise Module for Server Applications 15 | All versions | 2017+git1510945757.b2662641d5-5.22.1 |
| `ovmf` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2017+git1492060560.b6d11d7c46-4.26.1 |
| `ovmf` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 2017+git1510945757.b2662641d5-3.16.1 |
| `ovmf` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2017+git1492060560.b6d11d7c46-4.26.1 |
| `ovmf` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 2017+git1510945757.b2662641d5-3.16.1 |
| `ovmf` | openSUSE:Leap 15.0 | All versions | 2017+git1510945757.b2662641d5-lp150.4.19.1 |

Products: Tianocore Edk Ii.

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

Apply the vendor's patch.

## Is CVE-2019-0161 being exploited?

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

## Other vulnerabilities in Extensible Firmware Interface Development Kit (EDK II)

- [CVE-2018-12178](https://insights.sbomify.com/CVE-2018-12178/): Memory corruption in Extensible Firmware Interface Development Kit (EDK II) (critical 9.1)
- [CVE-2021-28216](https://insights.sbomify.com/CVE-2021-28216/): Memory corruption in EDK II (high 7.8)
- [CVE-2018-12179](https://insights.sbomify.com/CVE-2018-12179/): Privilege escalation in Extensible Firmware Interface Development Kit (EDK II) (high 7.8)
- [CVE-2018-3613](https://insights.sbomify.com/CVE-2018-3613/): Privilege escalation in Extensible Firmware Interface Development Kit (EDK II) (high 7.8)
- [CVE-2019-11098](https://insights.sbomify.com/CVE-2019-11098/): Other in Tianocore (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0161 is a medium-severity memory corruption vulnerability in Extensible Firmware Interface Development Kit (EDK II), published on 27 Mar 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-0161 in the wild and no public exploit code.

Affected product: Extensible Firmware Interface Development Kit (EDK II). 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-0161/ (Markdown: https://insights.sbomify.com/CVE-2019-0161/index.md)
```

## Sources

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

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