CVE DatabaseCVE-2018-19321
한국어 권고문 →
CVE-2018-193217.8/HIGHCISA KEV

GIGABYTE Drivers Arbitrary Physical Memory Read/Write Local Privilege Escalation (CVE-2018-19321)

⚡ 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)
3.7%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

GPCIDrv and GDrv kernel 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

A local attacker can exploit the exposed IOCTL interfaces to read/write arbitrary physical memory, leading to full kernel-level privilege escalation (SYSTEM)

Mitigation

Upgrade the affected GIGABYTE software to the latest secure versions, or completely uninstall the utilities and block the vulnerable driver files

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 the GIGABYTE utilities to their latest patched versions. If the software is not required for business operations, completely uninstall it using the following PowerShell commands:

powershell
# Identify and uninstall GIGABYTE software packages
$apps = Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like '*GIGABYTE*' }
foreach ($app in $apps) {
    Write-Output 'Uninstalling: $($app.Name)'
    $app.Uninstall()
}

2. Temporary Workaround & Hardening Configuration

Stop and delete the vulnerable driver service immediately, and delete the driver file from the system directory to prevent it from being loaded. Enable Microsoft Recommended Driver Block Rules or WDAC to block the driver hash.

cmd
:: Stop and delete the vulnerable GDrv service
sc stop GDrv
sc delete GDrv

:: Force delete the driver file from the system
del /f /q %SystemRoot%\gdrv.sys

3. Log Audit & IoC Verification Commands

Verify if the vulnerable driver is currently loaded or has been registered in the system event logs.

powershell
# Check if the vulnerable driver is currently loaded in the kernel
Get-CimInstance Win32_SystemDriver | Where-Object { $_.PathName -like '*gdrv*' -or $_.Name -like '*gdrv*' } | Format-Table Name, DisplayName, PathName, State

# Query System Event Logs for service installation events related to gdrv
Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045} | Where-Object { $_.Message -like '*gdrv*' } | Format-List TimeCreated, Message
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Due to active exploitation in BYOVD attacks, immediately uninstall legacy GIGABYTE utilities and enforce the Windows Recommended Driver Blocklist.

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 exists within the GPCIDrv and GDrv low-level kernel-mode drivers developed by GIGABYTE. These drivers are designed to facilitate hardware monitoring and overclocking from user-space utilities. However, they suffer from a critical design flaw where they expose input/output control (IOCTL) codes that allow arbitrary physical memory read and write operations without enforcing proper access controls or privilege checks. This allows any non-privileged local process to map and manipulate arbitrary physical memory addresses.

2. Exploitation Mechanics & Attack Scenario

An attacker must first obtain local execution capabilities on the target system. The attacker then opens a handle to the vulnerable driver's symbolic link (e.g., \\.\GDrv). By issuing specific IOCTL requests, the attacker can map physical memory into their user-space process. The attacker typically leverages this capability to locate the _EPROCESS structures of their own process and a system process (such as System PID 4) in memory, subsequently copying the security token of the system process to their own process (Token Stealing), thereby escalating privileges to NT AUTHORITY\SYSTEM. This driver is highly favored by threat actors in Bring Your Own Vulnerable Driver (BYOVD) campaigns to bypass modern OS-level security controls.

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 grants the attacker complete control over the compromised endpoint or server. With kernel-level privileges, attackers can disable endpoint detection and response (EDR) agents, terminate security software, install persistent kernel-mode rootkits, and facilitate lateral movement across the enterprise network, posing a severe threat to business operations and data integrity.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2018-19321)

FAQ

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

CVE-2018-19321 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 3.7%. 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-19321?

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-19321 before patching?

[Mitigation] Upgrade the affected GIGABYTE software to the latest secure versions, or completely uninstall the utilities and block the vulnerable driver files 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-19321

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-19321 GIGABYTE Drivers Arbitrary Physical Memory Read/Write Local Privilege Escalation (CVE-2018-19321) (CVSS 7.8) - Patch & Workaround | CVE Pulse