dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 14 Nov 2022. Known ransomware use
Aorus Graphics EngineApplication · Gigabyte

CVE-2018-19320

HIGH · 7.8 CVSS v3.1 Published 2018-12-21
Fix available
A fix is available. Upgrade to 1.26 / 1.57 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Ransomware Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GDrv kernel driver in multiple GIGABYTE utilities (APP Center, AORUS GRAPHICS ENGINE, XTREME GAMING ENGINE, OC GURU II) exposes a memcpy-like function callable from user-mode at ring0 privilege level. A local attacker can exploit this to write arbitrary data to kernel memory and escalate privileges to full system control.

MitigationRemove or disable the vulnerable GIGABYTE software components if not required, or apply vendor-provided patches when available. Limit local access to trusted personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aorus Graphics EngineApplication
Affected:< 1.57
App CenterApplication
Affected:< 19.0422.1
Oc Guru IiApplication
Affected:= 2.08
Xtreme Gaming EngineApplication
Affected:< 1.26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Gigabyte utilities
    Check Program Files and Program Files (x86) folders for Gigabyte Aorus Graphics Engine, Gigabyte App Center, Gigabyte Oc Guru II, or Xtreme Gaming Engine directories. Also check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Gigabyte entries.
    Affected if Any of these Gigabyte software packages are present on the system
  2. Check installed version of Gigabyte software
    Locate the main executable (e.g., AorusGraphicsEngine.exe, APPCenter.exe, OC_GURU_II.exe, or XTREME_GAMING_ENGINE.exe) in the installed directory. Right-click the executable, select Properties, and view the Version tab to obtain the precise version number.
    Affected if Version is below 1.57 for Aorus Graphics Engine, below 19.0422.1 for App Center, exactly 2.08 for Oc Guru II, or below 1.26 for Xtreme Gaming Engine
  3. Locate the GDrv kernel driver file
    Search for GDrv.sys in the system: check C:\Windows\System32\drivers\, the Gigabyte utility installation folder, and subfolders. Use command: dir /s C:\GDrv.sys
    Affected if The GDrv.sys driver file exists on the system
  4. Verify driver is currently loaded
    Open Command Prompt as Administrator and run: sc query GDrv or driverquery /v | findstr GDrv to check if the driver is currently active in memory.
    Affected if The GDrv driver shows a RUNNING state or appears in the list of active kernel drivers

A system is affected if any vulnerable Gigabyte software (Aorus Graphics Engine < 1.57, App Center < 19.0422.1, Oc Guru II = 2.08, or Xtreme Gaming Engine < 1.26) is installed with the GDrv.sys driver present and loaded in memory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.26 / 1.57 / 19.0422.1 or later
Fixed in 1.261.5719.0422.1
Interim mitigation

Remove or disable the vulnerable GIGABYTE software components if not required, or apply vendor-provided patches when available. Limit local access to trusted personnel only.

Recommended fix Moderate confidence

AORUS Graphics Engine 1.57+, Xtreme Gaming Engine 1.26+, App Center 19.0422.1+, OC Guru II (version after 2.08)

  1. 1. Identify which GIGABYTE utility is installed: AORUS Graphics Engine, App Center, Xtreme Gaming Engine, or OC Guru II
  2. 2. Uninstall the vulnerable version of the affected software
  3. 3. Download the latest version from the official GIGABYTE support website (www.gigabyte.com)
  4. 4. Install the updated version: AORUS Graphics Engine >= 1.57, Xtreme Gaming Engine >= 1.26, App Center >= 19.0422.1, or OC Guru II version > 2.08
  5. 5. Restart the system to ensure the new driver loads properly
  6. 6. Verify the installed version matches or exceeds the fixed release
Caveat None expected; this is a security update upgrading to a newer stable release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aorus Graphics Engine Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data