DirectIo64.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of DirectIo64.sys: vulnerable verdict, risk score 78/100. 2 YARA matches, 2/75 multi-engine detections. SHA256 d84e3e250a86227c. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

DirectIo64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver DirectIo64.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches2
Multi-engine detections2 / 75
File size42352 bytes
Code-signing signerDigiCert High Assurance EV Root CA
Analyzed2026-09-06
SHA256d84e3e250a86227c64a96f6d5ac2b447674ba93d399160850acb2339da43eae5
SHA1e44297a2b750ec1958bef265e2f1ae6fa4323b28
MD5afbb28a756e233d32e224a664763f79c

How the 78/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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface36 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (24)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00344305mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #193
0x00348F15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #965
0x00341315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1221
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00229305mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1217
0x0080BA0CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3715
0x0022BF0AmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #4034
0x0022BFE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #4090
0x0022B805mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3585
0x008002A2mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #168

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3C5A0x3E005.97CODE, EXEC, READ
.rdata0x083C0x0A003.56IDATA, READ
.data0x00180x02000.28IDATA, READ, WRITE
.pdata0x01A40x02003.38IDATA, READ
PAGE0x00B80x02002.5CODE, EXEC, READ
INIT0x08E80x0A004.89CODE, EXEC, READ, DISCARD
.reloc0x00180x02000.29IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (16)

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.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert High Assurance EV Root CA
Signer organisationDigiCert Inc
IssuerMicrosoft Code Verification Root
Serial61204DB4000000000027
Valid from2011-04-15 19:45 UTC
Valid until2021-04-15 19:55 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. 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 DirectIo64.sys

Is DirectIo64.sys safe?

Based on DriverShield static and dynamic analysis, DirectIo64.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of DirectIo64.sys?

DirectIo64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: d84e3e250a86227c64a96f6d5ac2b447674ba93d399160850acb2339da43eae5.

What is DirectIo64.sys?

DirectIo64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert High Assurance EV Root CA.

Related: Other drivers signed by DigiCert High Assurance EV Root CA · 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