Threats / GIGABYTE / CVE-2018-19320
CVE-2018-19320
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
GIGABYTE Multiple Products vulnerability
GIGABYTE driver exposes ring0 memcpy functionality allowing local attackers complete system control via multiple affected applications.
Verdict
Today item, not a backlog item.
A privilege escalation vulnerability in GIGABYTE's low-level driver enables local code execution with kernel privileges. Active exploitation and ransomware deployment confirm critical risk to affected systems.
CISA KEV Yes · 2022-10-244Ransomware use Flagged4EPSS 0.03597 (verify live)5Exploit Public PoC6CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
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
8 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.03597 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: GIGABYTE, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1403 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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 access to a system running vulnerable GIGABYTE software.
Business
User systems become entry points for post-compromise lateral movement and persistence.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the GDrv driver's exposed ring0 memcpy functionality to write arbitrary kernel memory.
Business
Security controls and kernel protections are bypassed, eliminating OS-level defenses.
3
Lateral reach — past segmentation narrative 3
Attacker
I achieve kernel-level code execution and establish complete system control.
Business
Attackers gain unrestricted access to sensitive data, system resources, and ability to persist undetected.
4
Data at risk — exfiltration narrative 4
Attacker
I deploy ransomware or additional malware with kernel privileges.
Business
Operations are disrupted, data is encrypted or exfiltrated, and recovery costs escalate significantly.
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