CVE-2018-19320.sys - Malicious (88/100) - DriverShield Analysis

Analysis of CVE-2018-19320.sys: malicious verdict, risk score 88/100. 4 YARA matches, 10/75 multi-engine detections. SHA256 31f4cfb4c71da441. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

CVE-2018-19320.sys - Analysis Report

DriverShield analyzed the Windows kernel driver CVE-2018-19320.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches4
Multi-engine detections10 / 75
File size26192 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-04-02
SHA25631f4cfb4c71da44120752721103a16512444c13c2ac2d857a7e6f13cb679b427
SHA1fe10018af723986db50701c8532df5ed98b17c39
MD59ab9f3b75a2eb87fafb1b7361be9dfb3

Driver identity

Version resource data embedded in the CVE-2018-19320.sys PE header, as extracted by the analysis engine.

File descriptionGIGABYTE Tools
ProductWindows (R) Server 2003 DDK driver
CompanyWindows (R) Server 2003 DDK provider
Original filenamegdrv.sys
Internal namegdrv.sys
File version5.2.3790.1830 built by: WinDDK
Copyright© Microsoft Corporation. All rights reserved.

How the 88/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

Kernel-mode APIs resolved from the Import Address Table of CVE-2018-19320.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (16)

Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.

CodeSeverityTransferDescription
0xC3502808critical (known exploit)METHOD_BUFFEREDArbitrary memory R/W (RTCore64)
0xC350280Ccritical (known exploit)METHOD_BUFFEREDPhysical memory map (RTCore64)
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0xC350A440mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2320
0xC350A444mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2321
0xC350A448mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2322
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00226B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2757
0x00343846mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3601
0xC3500E68mediumMETHOD_BUFFEREDCUSTOM_MSI Function #922
0xC3500E6CmediumMETHOD_BUFFEREDCUSTOM_MSI Function #923
0xC3506404mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2305
0xC3502844mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2577
0xC3506408mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2306
0xC350B941mediumMETHOD_IN_DIRECTCUSTOM_MSI Function #3664
0x00340388mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #226

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2DC80x2E006.24CODE, EXEC, READ
.rdata0x06100x08003.59IDATA, READ
.data0x01580x02000.3IDATA, READ, WRITE
.pdata0x02DC0x04003.17IDATA, READ
INIT0x04120x06003.77CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03E80x04003.41IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Windowsrserverddkprovider_Gdrvsys_Windowsrserverddkdriver_8899mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - gdrv.sys
VULN_RTCore64criticalMSI RTCore64.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 18 paths explored at a maximum depth of 18. Vulnerability classes reached: 1. Exploitable paths: 0.

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about CVE-2018-19320.sys

Is CVE-2018-19320.sys safe?

Based on DriverShield static and dynamic analysis, CVE-2018-19320.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of CVE-2018-19320.sys?

CVE-2018-19320.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 31f4cfb4c71da44120752721103a16512444c13c2ac2d857a7e6f13cb679b427.

What is CVE-2018-19320.sys?

CVE-2018-19320.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact