CVE DatabaseCVE-2018-19322
한국어 권고문 →
CVE-2018-193227.8/HIGHCISA KEVCWE-749

GIGABYTE Drivers (GPCIDrv/GDrv) Privilege Escalation and Kernel Code Execution (CVE-2018-19322)

⚡ Jump to Patch
Affected Vendors
gigabyte
Affected Components
app center, aorus graphics engine, xtreme gaming engine, oc guru ii
Published Date
2018-12-21
CVSS v3.1
7.8
HIGH
EPSS (30d)
1.8%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

GPCIDrv and GDrv drivers bundled with 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

Impact

Local attackers can exploit the exposed IO port read/write functionality to execute arbitrary code with kernel-level privileges (SYSTEM) and bypass security controls

Mitigation

Update the affected GIGABYTE utilities to their latest secure versions, or block and remove the vulnerable drivers using Windows Defender Application Control (WDAC)

Affected Products & Version Scope

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

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

Update all GIGABYTE utility software to the latest versions. To remove legacy software and stop the vulnerable driver services, execute the following PowerShell commands:

powershell
# Stop and disable the vulnerable GDrv service
Stop-Service -Name 'GDrv' -ErrorAction SilentlyContinue
Set-Service -Name 'GDrv' -StartupType Disabled -ErrorAction SilentlyContinue

# Uninstall legacy GIGABYTE applications
Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like '*GIGABYTE*' } | ForEach-Object { 
    Write-Host 'Uninstalling: ' $_.Name
    $_.Uninstall() 
}

2. Temporary Workaround & Hardening Configuration

If immediate patching is not feasible, enable the Microsoft Vulnerable Driver Blocklist to prevent the driver from loading. Apply the following registry configuration:

reg
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Config]
"VulnerableDriverBlocklistEnable"=dword:00000001

3. Log Audit & IoC Verification Commands

Use the following PowerShell script to scan the system for the presence of the vulnerable gdrv.sys driver and verify if it is currently loaded in memory:

powershell
# Scan for the vulnerable gdrv.sys file
$DriverPath = Get-ChildItem -Path 'C:\Windows\System32\drivers' -Filter 'gdrv.sys' -Recurse -ErrorAction SilentlyContinue
if ($DriverPath) {
    Write-Host '[WARNING] Vulnerable GIGABYTE driver file detected:' $DriverPath.FullName -ForegroundColor Red
} else {
    Write-Host '[OK] No vulnerable gdrv.sys file found in drivers directory.' -ForegroundColor Green
}

# Check if the driver is currently loaded in memory
$LoadedDriver = Get-WmiObject Win32_SystemDriver | Where-Object { $_.Name -eq 'GDrv' -or $_.PathName -like '*gdrv.sys*' }
if ($LoadedDriver) {
    Write-Host '[ALERT] Vulnerable GIGABYTE driver is currently LOADED in memory!' -ForegroundColor Red
} else {
    Write-Host '[OK] Vulnerable driver is not loaded.' -ForegroundColor Green
}
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Immediately update GIGABYTE utilities to the latest versions and enforce the Windows Vulnerable Driver Blocklist to mitigate BYOVD risks.

Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot

Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.

100% MITRE ATT&CK Detection · 1-Click Rollback

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability (CVE-2018-19322) is an exposed dangerous function vulnerability (CWE-749) residing in the GPCIDrv and GDrv kernel-mode drivers utilized by GIGABYTE hardware utility software. These drivers expose control codes that allow user-mode applications to read and write directly to hardware IO ports without proper privilege verification. This design flaw allows any local process to bypass operating system access controls and interact directly with kernel memory space.

2. Exploitation Mechanics & Attack Scenario

An attacker with low-privilege local access can leverage the 'Bring Your Own Vulnerable Driver' (BYOVD) technique. By dropping and loading the legitimately signed but vulnerable GIGABYTE driver, the attacker evades driver signature enforcement policies. The attacker then issues specific IOCTL (Input/Output Control) requests to the driver to map physical memory or write directly to IO ports. This capability is typically exploited to overwrite process tokens in kernel memory, elevating the attacker's privileges to NT AUTHORITY\SYSTEM or executing arbitrary payloads in ring 0.

3. Infrastructure & Business Impact

As a CISA KEV-listed vulnerability, this flaw is actively exploited in the wild by advanced persistent threat (APT) groups and ransomware operators. Successful exploitation allows attackers to disable endpoint security agents (EDR/AV) operating at the kernel level. This facilitates persistent access, credential dumping, and subsequent lateral movement across the enterprise network, posing a severe risk of full domain compromise and ransomware deployment.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2018-19322)

FAQ

Q1. How critical is CVE-2018-19322 and is it actively exploited in the wild?

CVE-2018-19322 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 1.8%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2018-19322?

Primary impacted vendors include gigabyte across app center, aorus graphics engine, xtreme gaming engine, oc guru ii. Scope summary: 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

Q3. What temporary mitigations or workarounds exist for CVE-2018-19322 before patching?

[Mitigation] Update the affected GIGABYTE utilities to their latest secure versions, or block and remove the vulnerable drivers using Windows Defender Application Control (WDAC) Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2018-19322

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (gigabyte)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2018-19322 GIGABYTE Drivers (GPCIDrv/GDrv) Privilege Escalation and Kernel Code Execution (CVE-2018-19322) (CVSS 7.8) - Patch & Workaround | CVE Pulse