Threats / GIGABYTE / CVE-2018-19321
CVE-2018-19321
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
GIGABYTE Multiple Products vulnerability
GIGABYTE drivers GPCIDrv and GDrv in App Center, AORUS Graphics Engine, XTREME Gaming Engine, and OC GURU II allow arbitrary physical memory read/write, enabling local privilege escalation.
Verdict
Today item, not a backlog item.
A local attacker can exploit exposed driver functionality to read and write arbitrary physical memory, bypassing access controls and escalating privileges on affected systems.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-10-24), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.03671 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: GIGABYTE, Multiple Products. Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain local code execution on a target system running vulnerable GIGABYTE software.
Business
An insider or compromised user account becomes a foothold for further attack.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I invoke the vulnerable driver to read and write arbitrary physical memory regions.
Business
Security boundaries enforced by the operating system are circumvented.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify kernel memory or security structures to escalate my privileges to system level.
Business
The attacker gains unrestricted control over the affected machine.
4
Data at risk — exfiltration narrative 4
Attacker
I establish persistence and deploy malware, ransomware, or lateral movement tools.
Business
The organization faces data theft, encryption attacks, or network compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05