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

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

VBoxDrv.sys - Analysis Report

DriverShield analyzed the Windows kernel driver VBoxDrv.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	3
Multi-engine detections	0 / 75
File size	115856 bytes
Code-signing signer	VeriSign Time Stamping Services Signer - G2
Analyzed	2026-09-06
SHA256	1684e24dae20ab83ab5462aa1ff6473110ec53f52a32cfb8c1fe95a2642c6d22
SHA1	cf040040628b58f4a811f98c2690913c1e8e4e3c
MD5	84d67136a7cefb266734ff56029041e3

Driver identity

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

File description	VirtualBox Support Driver
Product	Sun VirtualBox
Company	Sun Microsystems, Inc.
Original filename	VBoxDrv.sys
Internal name	VBoxDrv.sys
File version	3.0.0.r49315
Copyright	Copyright (C) 2009 Sun Microsystems, 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.

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

Kernel imports (20)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemory	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
DbgPrint	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign

IOCTL dispatch codes (35)

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
0x00228107	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #65
0x0022810B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #66
0x00228103	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #64
0x008000B3	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #44
0x00802083	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2080
0x00800C8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #802
0x00801883	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1568
0x00803883	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3616
0x00803C83	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3872
0x0080840F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #259
0x0080F045	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #3089
0x00228010	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #4
0x00221FE8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #2042
0x00801886	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #1569
0x00800086	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #33
0x00802486	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #2337
0x0080008E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #35
0x0080208E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #2083
0x00800486	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #289
0x00800082	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #32
0x008000BA	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #46
0x00800096	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #37
0x008038B8	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #3630
0x00803080	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #3104

Showing 24 of 35 extracted control codes.

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	0x1054E	0x10580	6.42	CODE, EXEC, READ
.rdata	0x37D9	0x3800	5.69	IDATA, READ
.data	0x367C	0x3680	2.13	IDATA, READ, WRITE
.edata	0x1A3B	0x1A40	5.67	IDATA, READ
INIT	0x0746	0x0780	5.38	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x0398	0x03C0	3.19	IDATA, READ, DISCARD
.reloc	0x0DE4	0x0E00	6.35	IDATA, READ, 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.

YARA rule matches (3)

Rule	Severity	Detects
PUA_VULN_Driver_Sunmicrosystemsinc_Vboxdrvsys_Sunvirtualbox_R_7539	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - VBoxDrv.sys. Investigate matches in context: expected filenames or standard ...
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003	OS Credential Dumping	Credential Access
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1006	Direct Volume Access	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	VeriSign Time Stamping Services Signer - G2
Signer organisation	VeriSign, Inc.
Issuer	VeriSign Time Stamping Services CA
Serial	3825D7FAF861AF9EF490E726B5D65AD5
Valid from	2007-06-15 00:00 UTC
Valid until	2012-06-14 23:59 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: VeriSign Time Stamping Services CA
• Chain: VeriSign Class 3 Code Signing 2004 CA
• Chain: Sun Microsystems, Inc.

Symbolic execution

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

Frequently asked questions about VBoxDrv.sys

Is VBoxDrv.sys safe?

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

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

What is VBoxDrv.sys?

VBoxDrv.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by VeriSign Time Stamping Services Signer - G2.

Related: Other drivers signed by VeriSign Time Stamping Services Signer - 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