Threats / GIGABYTE / CVE-2018-19323
CVE-2018-19323
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
GIGABYTE Multiple Products vulnerability
GIGABYTE low-level drivers in App Center and gaming software expose arbitrary physical memory read/write, enabling local privilege escalation.
Verdict
Today item, not a backlog item.
Local attackers can exploit memory access in GPCIDrv and GDrv drivers to bypass access controls and gain elevated system privileges. Active exploitation and ransomware deployment have been observed.
CISA KEV Yes · 2022-10-244Ransomware use Flagged4EPSS 0.07828 (verify live)5Exploit Public PoC6CVSS 9.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
2 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.07828 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/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 code execution as an unprivileged local user on a system running GIGABYTE App Center or gaming software.
Business
User systems running GIGABYTE utilities are exposed to local compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I load or interact with the vulnerable GPCIDrv or GDrv drivers to access arbitrary physical memory locations.
Business
Driver-level access control mechanisms fail to restrict memory operations.
3
Lateral reach — past segmentation narrative 3
Attacker
I read and write kernel memory to modify security structures or inject malicious code into privileged processes.
Business
System integrity is compromised; kernel-level protections are bypassed.
4
Data at risk — exfiltration narrative 4
Attacker
I escalate my privileges to SYSTEM or kernel level, gaining full control of the compromised machine.
Business
Complete system takeover enables data theft, malware installation, and lateral movement.
5
Lights out — disruption & extortion narrative 5
Attacker
I deploy ransomware or other persistent threats across affected systems in targeted environments.
Business
Organizations face operational disruption, data loss, and financial extortion.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.