Skip to content

CVE-2018-19322

The GPCIDrv and GDrv low-level drivers in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC…

High Known exploited
Severity
7.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.82%
Chance of exploitation in the next 30 days. Higher than 78.69% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Oct 24, 2022
Weakness
CWE-749 Exposed Dangerous Method or Function
Fix
None yet
No fixed version published
Exploited in the wild. GIGABYTE Multiple Products Code Execution Vulnerability (GIGABYTE Multiple Products). Required action: Apply updates per vendor instructions. Due for U.S. federal agencies by Nov 14, 2022. Known to be used in ransomware campaigns.

Description

The GPCIDrv and GDrv low-level drivers 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 expose functionality to read/write data from/to IO ports. This could be leveraged in a number of ways to ultimately run code with elevated privileges.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.8

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-749: Exposed Dangerous Method or Function

The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.

How to prevent it
  • Architecture and Design: If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
  • Architecture and Design, Implementation: Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.

References

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-wf6j-gr27-g7ch
GeoServer has a Server-Side Template Injection (SSTI) vulnerability in processing FreeMarker templates
High Same weakness, CWE-749
GHSA-7f3r-gwc9-2995
view_component: Preview Route Can Dispatch Inherited Helper Methods
Medium Same weakness, CWE-749
GHSA-grj5-jjm8-h35p
VM2 Sandbox Breakout Through __lookupGetter__
Critical Same weakness, CWE-749
GHSA-j4p8-h8mh-rh8q
Self-hosted n8n has Legacy Code node that enables arbitrary file read/write
Medium Same weakness, CWE-749
GHSA-3q2w-42mv-cph4
filebrowser Allows Shell Commands to Spawn Other Commands
High Same weakness, CWE-749
GHSA-m37h-8r48-2cxj
H2O Vulnerable to Execution of Arbitrary Files
Medium Same weakness, CWE-749
GHSA-7qwv-cwgj-c8rj
Improper Input Validation in Apache Struts
High Known exploited Same weakness, CWE-749
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor