# CVE-2018-19320: GIGABYTE Multiple Products Unspecified

> A local attacker can exploit ring0 memory access in GIGABYTE utilities to gain complete system control.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 24 Oct 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2018
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-wg2v-fx2j-3jrr

## What is CVE-2018-19320?

CVE-2018-19320 is a high-severity vulnerability in n/a, published on 21 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system.

## Which versions are affected by CVE-2018-19320?

It affects 4 products.


Products: Gigabyte Aorus Graphics Engine, Gigabyte App Center, Gigabyte Oc Guru Ii, Gigabyte Xtreme Gaming Engine.

## How do I fix CVE-2018-19320?

No fix has been published for CVE-2018-19320 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Nov 2022.

## Is CVE-2018-19320 being exploited?

Yes. Attackers have exploited CVE-2018-19320 in the wild since at least 24 Oct 2022, including in ransomware campaigns.

Public exploit code:

- Unsigned driver loader using CVE-2018-19320 (github_poc): https://github.com/zer0condition/GDRVLoader
- Exploiting ring0 memcpy-like functionality to disable Driver Signing Enforcement (DSE) (github_poc): https://github.com/ASkyeye/CVE-2018-19320
- CVE-2018-19320 LPE Exploit (github_poc): https://github.com/hmnthabit/CVE-2018-19320-LPE

## Other vulnerabilities in n/a

- [CVE-2018-19323](https://insights.sbomify.com/CVE-2018-19323/): GIGABYTE Multiple Products Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2018-19321](https://insights.sbomify.com/CVE-2018-19321/): GIGABYTE Multiple Products Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2018-19322](https://insights.sbomify.com/CVE-2018-19322/): GIGABYTE Multiple Products Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19320 and fix it if it is affected.

What it is: CVE-2018-19320 is a high-severity vulnerability in n/a, published on 21 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-19320 in the wild since at least 24 Oct 2022, including in ransomware campaigns.

Affected product: n/a. 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-2018-19320/ (Markdown: https://insights.sbomify.com/CVE-2018-19320/index.md)
```

## Sources

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

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