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

Analysis of AsIO3.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 f46237638a8ea0ae. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

AsIO3.sys - Analysis Report

DriverShield analyzed the Windows kernel driver AsIO3.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 matches3
Multi-engine detections0 / 76
File size60040 bytes
Code-signing signerDigiCert Trusted Root G4
Analyzed2026-04-02
SHA256f46237638a8ea0ae4b46e9560ce55346c12dec1624b9e096ea405f80e29b8314
SHA1193fe1ab189a65c9cb353af52fa456c338dbc864
MD55a33427a0329f25c3f5a80d8823e13ff

Driver identity

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

File descriptionAsIO3 Driver
ProductAsIO3
CompanyAsustek Computer Inc.
Internal nameAsIO3
File version1.02.41
CopyrightCopyright (C) 2022 Asustek Computer Inc.

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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface36 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (29)

Kernel-mode APIs resolved from the Import Address Table of AsIO3.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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 29 resolved.

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
0x0022341FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00803F0DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4035
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0022CBE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #762
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x00340115mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #69
0x00800A00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #640
0x003402A0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #168
0x0034002EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #11
0x98768869mediumMETHOD_IN_DIRECTCUSTOM_PROCESS Function #538

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x6CDA0x6E006.4CODE, EXEC, READ
.rdata0x093C0x0A004.07IDATA, READ
.data0x04900x02003.58IDATA, READ, WRITE
.pdata0x02400x04002.61IDATA, READ
PAGE0x01680x02004.61CODE, EXEC, READ
INIT0x070E0x08004.83CODE, EXEC, READ, DISCARD
.rsrc0x03000x04002.59IDATA, READ, DISCARD
.reloc0x00180x02000.3IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (3)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (18)

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
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted Root G4
Signer organisationDigiCert Inc
IssuerDigiCert High Assurance EV Root CA
SerialFD1BBCA796BD7F8DD4C82E10A9A9631
Valid from2022-01-13 00:00 UTC
Valid until2031-11-09 23:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about AsIO3.sys

Is AsIO3.sys safe?

Based on DriverShield static and dynamic analysis, AsIO3.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 AsIO3.sys?

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

What is AsIO3.sys?

AsIO3.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 Trusted Root G4.

Related: Other drivers signed by DigiCert Trusted Root G4 · 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