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

Analysis of MsIo64.sys: vulnerable verdict, risk score 72/100. 1 YARA match, 1/76 multi-engine detections. SHA256 d636c011b8b28965. 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).

VerdictVulnerable (72/100)
YARA matches1
Multi-engine detections1 / 76
File size19000 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-04-14
SHA256d636c011b8b2896572f5de260eb997182cc6955449b044a739bd19cbe6fdabd2
SHA11de9f25d189faa294468517b15947a523538ce9d
MD561b068b10abfa0776f3b96a208d75bf9

Driver identity

Version resource data embedded in the MsIo64.sys PE header, as extracted by the analysis engine.

File descriptionMICSYS IO driver
ProductMsIo64 Driver Version 1.3
CompanyMICSYS Technology Co., LTd
Original filenameMsIo64.sys
Internal nameMsIo64.sys
File version1.3 x64 built by: WinDDK
CopyrightCopyright (c) 2021 MICSYS

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.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches5 / 100
Dangerous kernel imports78 / 100
IOCTL dispatch surface15 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference40 / 100

Kernel imports (12)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (5)

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
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0034032CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #203
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0E1F0x10005.71CODE, EXEC, READ
.rdata0x01E80x02004.16IDATA, READ
.data0x015C0x02000.62IDATA, READ, WRITE
.pdata0x00600x02000.82IDATA, READ
INIT0x02B20x04003.64CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03900x04003.1IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
PUA_VULN_Driver_Micsystechnologycoltd_Msiosys_Msiodriverversion_X_AE42mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - MsIo64.sys

MITRE ATT&CK techniques (7)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1543.003Windows ServicePersistence
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000005635887EDE1882EF76000000000056
Valid from2022-06-07 18:08 UTC
Valid until2023-06-01 18:08 UTC (expired)
Signature validityNot verified

Associated CVEs

Symbolic execution

Engine angr, status completed, 39 paths explored at a maximum depth of 39. 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: d636c011b8b2896572f5de260eb997182cc6955449b044a739bd19cbe6fdabd2.

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 Microsoft Windows Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · CVE-2020-17382 · 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