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-19322

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 GPCIDrv and GDrv low-level drivers 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 expose functionality to read/write data from/to IO ports. This could be leveraged in a number of ways to ultimately run code with elevated privileges.

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 GPCIDrv and GDrv low-level drivers in multiple GIGABYTE utilities (APP Center, AORUS GRAPHICS ENGINE, XTREME GAMING ENGINE, OC GURU II) expose direct IO port read/write functionality to user-mode processes. This allows unprivileged users to perform privileged I/O operations, which can be chained to achieve arbitrary code execution with elevated (SYSTEM) privileges.

MitigationUpdate all affected GIGABYTE software to versions greater than v1.05.21 for APP Center, v1.57 for AORUS GRAPHICS ENGINE, v1.26 for XTREME GAMING ENGINE, and v2.08 for OC GURU II. Alternatively, remove or disable these drivers if not required.

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:<= 1.05.21
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. Check for vulnerable Gigabyte applications
    Inspect installed programs for AORUS GRAPHICS ENGINE, GIGABYTE APP CENTER, OC GURU II, or XTREME GAMING ENGINE. Use Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check Program Files directories.
    Affected if Any of these applications are installed with version below the fixed releases (Aorus Graphics Engine < 1.57, App Center <= 1.05.21, Oc Guru II = 2.08, Xtreme Gaming Engine < 1.26)
  2. Identify vulnerable driver files on disk
    Search for GPCIDrv.sys and GDrv.sys files in system directories: C:\Windows\System32\drivers\ and C:\Windows\SysWOW64\drivers\.
    Affected if Either GPCIDrv.sys or GDrv.sys file exists on the system
  3. Check driver registry entries
    Query registry under HKLM\SYSTEM\CurrentControlSet\Services for GPCIDrv or GDrv entries using reg query command.
    Affected if Registry entries for GPCIDrv or GDrv drivers exist in the service database
  4. Verify driver version information
    Right-click on driver files and view Properties > Details for version information, or use PowerShell Get-ItemProperty on the driver files.
    Affected if Driver version is present and matches vulnerable driver releases associated with the affected applications

The system is affected if any vulnerable Gigabyte software (Aorus Graphics Engine, App Center, Oc Guru II, Xtreme Gaming Engine) is installed with versions prior to the fixed releases AND the GPCIDrv or GDrv low-level drivers are present on the system.

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 or later
Fixed in 1.261.57
Interim mitigation

Update all affected GIGABYTE software to versions greater than v1.05.21 for APP Center, v1.57 for AORUS GRAPHICS ENGINE, v1.26 for XTREME GAMING ENGINE, and v2.08 for OC GURU II. Alternatively, remove or disable these drivers if not required.

Recommended fix High confidence

AORUS GRAPHICS ENGINE >= 1.57, XTREME GAMING ENGINE >= 1.26, APP Center > 1.05.21

  1. Identify the exact installed version of Gigabyte software (AORUS GRAPHICS ENGINE, XTREME GAMING ENGINE, APP Center, or OC GURU II) using Add/Remove Programs or the application's About/Help section
  2. Navigate to the official GIGABYTE support website: https://www.gigabyte.com/
  3. Locate the Downloads/Support section for your specific product
  4. Download the latest version: AORUS GRAPHICS ENGINE version 1.57 or later, XTREME GAMING ENGINE version 1.26 or later, or APP Center version newer than 1.05.21
  5. Close any running Gigabyte applications
  6. Uninstall the current vulnerable version of the software
  7. Install the downloaded fixed version
  8. Restart the system to ensure driver components are properly loaded
Caveat Verify compatibility with your specific GPU model and Windows version before upgrading; some legacy features may have been removed in newer versions

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

Fix this in Aorus Graphics Engine Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19322 — 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-19322 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