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

Analysis of AsrDrv.sys: vulnerable verdict, risk score 72/100. 4 YARA matches, 1/75 multi-engine detections. SHA256 2003b478b9fd1b3d. 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 matches4
Multi-engine detections1 / 75
File size34568 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA2562003b478b9fd1b3d76ec5bf4172c2e8915babbbee7ad1783794acbf8d4c2519d
SHA115d1a6a904c8409fb47a82aefa42f8c3c7d8c370
MD57c72a7e1d42b0790773efd8700e24952

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.00.0000 built by: WinDDK
CopyrightCopyright (C) 2012 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 matches90 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface30 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (20)

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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (10)

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
0x0022E808mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2562
0x0022E85CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2583
0x00341705mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1473
0x00340305mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #193
0x00225F15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1989
0x0080B389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3298
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00340340mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #208

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x22380x24006.12CODE, EXEC, READ
.rdata0x07C40x08004.39IDATA, READ
.data0x031C0x04001.12IDATA, READ, WRITE
.pdata0x02B80x04003.1IDATA, READ
PAGE0x1A470x1C006.04CODE, EXEC, READ
INIT0x093A0x0A005.15CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03A00x04003.05IDATA, READ, DISCARD
.reloc0x00600x02000.32IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Asrockincorporation_Asrdrvsys_Asrockiodriver_2003mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - AsrDrv103.sys. Investigate matches in context: expected filenames or standar...
PUA_VULN_Driver_Asrockincorporation_Asrdrvsys_Asrockiodriver_4D03mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - AsrDrv.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (14)

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.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
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

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

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 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: 2003b478b9fd1b3d76ec5bf4172c2e8915babbbee7ad1783794acbf8d4c2519d.

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 Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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