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

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

AsrDrv.sys - Analysis Report

DriverShield analyzed the Windows kernel driver AsrDrv.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 / 74
File size68208 bytes
Code-signing signerGlobalSign
Analyzed2026-08-15
SHA256837f499e9cd8e2774e66f001fc363e2dc5cf96cebb02a2778ca819c927430599
SHA1c9f89081ff1b04fdd6f6cb02f4aa3c89d8352f5d
MD5867748f9c9ce55abb8bea32b34dc57ee

Driver identity

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

File descriptionASRock IO Driver
ProductASRock IO Driver
CompanyASRock Incorporation
Original filenameAsrDrv.sys
Internal nameAsrDrv.sys
File version1.00.02.0000
CopyrightCopyright (C) 2024 ASRock Incorporation

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

Kernel imports (25)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
DbgPrintExlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (14)

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
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022E84CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2579
0x0022E838mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2574
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x003463E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2298
0x00341315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1221
0x00800548mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #338
0x00224B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #709
0x00800020mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #8
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00340320mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #200
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x589E0x5A005.68CODE, EXEC, READ
.rdata0x0DF40x0E004.34IDATA, READ
.data0x16800x04001.26IDATA, READ, WRITE
.pdata0x04080x06003.08IDATA, READ
PAGE0x1C8C0x1E006.1CODE, EXEC, READ
INIT0x0C2E0x0E004.95CODE, EXEC, READ, DISCARD
.rsrc0x04080x06002.57IDATA, READ, DISCARD
.reloc0x00300x02000.58IDATA, 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
MAL_DSEBypasscriticalDSE bypass attempt

MITRE ATT&CK techniques (15)

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
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 Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign
Signer organisationGlobalSign
IssuerGlobalSign Root CA
Serial1EE5F169DFF97352B6465D66A
Valid from2018-09-19 00:00 UTC
Valid until2028-01-28 12:00 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about AsrDrv.sys

Is AsrDrv.sys safe?

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

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

What is AsrDrv.sys?

AsrDrv.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign.

Related: Other drivers signed by GlobalSign · 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