MSIO64.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of MSIO64.sys: vulnerable verdict, risk score 72/100. 0 YARA matches, 1/75 multi-engine detections. SHA256 525d9b51a80ca0cd. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

MSIO64.sys - Analysis Report

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

Verdict	Vulnerable (72/100)
YARA matches	0
Multi-engine detections	1 / 75
File size	25616 bytes
Code-signing signer	Symantec Class 3 Extended Validation Code Signing CA - G2
Analyzed	2026-09-06
SHA256	525d9b51a80ca0cd4c5889a96f857e73f3a80da1ffbae59851e0f51bdfb0b6cd
SHA1	e6305dddd06490d7f87e3b06d09e9d4c1c643af0
MD5	d9e7e5bcc5b01915dbcef7762a7fc329

How the 72/100 score breaks down

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

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	0 / 100
Dangerous kernel imports	78 / 100
IOCTL dispatch surface	9 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	40 / 100

Kernel imports (10)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
DbgPrint	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign

IOCTL dispatch codes (3)

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.

Code	Severity	Transfer	Description
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x008002A2	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #168

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x0F35	0x1000	5.89	CODE, EXEC, READ
.rdata	0x0160	0x0200	3.09	IDATA, READ
.data	0x0110	0x0200	0.3	IDATA, READ, WRITE
.pdata	0x0054	0x0200	0.75	IDATA, READ
INIT	0x0262	0x0400	3.27	CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Class 3 Extended Validation Code Signing CA - G2
Signer organisation	Symantec Corporation
Issuer	VeriSign Class 3 Public Primary Certification Authority - G5
Serial	191A32CB759C97B8CFAC118DD5127F49
Valid from	2014-03-04 00:00 UTC
Valid until	2024-03-03 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: MICSYS Technology Co., Ltd.
Chain: VeriSign Class 3 Public Primary Certification Authority - G5

Associated CVEs

CVE-2020-17382 - MSI Ambient Link driver - physical memory access

Symbolic execution

Engine angr, status completed, 27 paths explored at a maximum depth of 27. 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 MSIO64.sys

Is MSIO64.sys safe?

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

What is the risk score of MSIO64.sys?

MSIO64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 525d9b51a80ca0cd4c5889a96f857e73f3a80da1ffbae59851e0f51bdfb0b6cd.

What is MSIO64.sys?

MSIO64.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 Class 3 Extended Validation Code Signing CA - G2.