# CVE-2019-5098: Memory corruption in AMD ATI

> A crafted pixel shader in the AMD GPU driver causes an out-of-bounds read, potentially allowing code execution or privilege escalation from a virtual machine guest to the host.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-69g2-j5hm-jq2w

## What is CVE-2019-5098?

CVE-2019-5098 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 5 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. A specially crafted pixel shader can cause out-of-bounds memory read. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered from VMware guest, affecting VMware host.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 3 products.


Products: Amd Radeon 550 Firmware, Amd Radeon Rx 550 Firmware, Vmware Workstation.

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

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

## Is CVE-2019-5098 being exploited?

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

## Other vulnerabilities in Vmware Workstation

- [CVE-2019-5049](https://insights.sbomify.com/CVE-2019-5049/): Memory corruption in AMD ATI (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5098 is a high-severity memory corruption vulnerability in Vmware Workstation, published on 5 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5098 in the wild and no public exploit code.

Affected product: Vmware Workstation. 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-5098/ (Markdown: https://insights.sbomify.com/CVE-2019-5098/index.md)
```

## Sources

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

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