CVE-2018-19320
GIGABYTE Multiple Products Unspecified Vulnerability
GIGABYTE Multiple Products
The GDrv low-level driver in 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 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 24 October 2022. US federal agencies were required to remediate it by 14 November 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 3.6%, which is higher than 89.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2018-19320 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-19320.
What does CVE-2018-19320 affect?
CVE-2018-19320 affects GIGABYTE Multiple Products. The GDrv low-level driver in 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 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system.
How severe is CVE-2018-19320?
CVE-2018-19320 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 3.6%, higher than 89.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 14 November 2022.
How should organisations respond to CVE-2018-19320?
Apply the vendor patch for GIGABYTE Multiple Products as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.