Analysis of vbox.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 46/75 multi-engine detections. SHA256 cf3a7d4285d65bf8. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver vbox.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 | 2 |
| Multi-engine detections | 46 / 75 |
| File size | 68288 bytes |
| Code-signing signer | innotek GmbH |
| Analyzed | 2026-09-06 |
| SHA256 | cf3a7d4285d65bf8688215407bce1b51d7c6b22497f09021f0fce31cbeb78986 |
| SHA1 | 7c1b25518dee1e30b5a6eaa1ea8e4a3780c24d0c |
| MD5 | eaea9ccb40c82af8f3867cd0f4dd5e9d |
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 | 80 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 36 / 100 |
| Known-vulnerable corpus | 100 / 100 |
| Code-signing state | 80 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of vbox.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 |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| KeDelayExecutionThread | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| KeSetEvent | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| DbgPrint | low | Standard kernel API - generally benign |
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 |
|---|---|---|---|
| 0x0022830B | high | METHOD_NEITHER | FILE_DEVICE_UNKNOWN Function #194 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00226BE8 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2810 |
| 0x0022EBE9 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #2810 |
| 0x00808689 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #418 |
| 0x008024BC | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2351 |
| 0x00228218 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #134 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x0034930D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #1219 |
| 0x0034230D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #2243 |
| 0x0080F981 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3680 |
| 0x0080F2B1 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3244 |
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 | 0x856E | 0x8580 | 6.2 | CODE, EXEC, READ |
| .rdata | 0x2A58 | 0x2A60 | 5.6 | IDATA, READ |
| .data | 0x1D00 | 0x1D00 | 1.97 | IDATA, READ, WRITE |
| .pdata | 0x0CF0 | 0x0D00 | 4.66 | IDATA, READ |
| .edata | 0x0A72 | 0x0A80 | 5.33 | IDATA, READ |
| INIT | 0x0638 | 0x0640 | 4.86 | CODE, EXEC, READ, WRITE, DISCARD |
| .reloc | 0x013C | 0x0140 | 3.71 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Not enabled |
| DEP | Not enabled |
| Integrity check | Not enforced |
| Mitigation score | 5 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
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 |
| T1562.001 | Impair Defenses | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | innotek GmbH |
|---|---|
| Signer organisation | innotek GmbH |
| Issuer | GlobalSign ObjectSign CA |
| Serial | 10000000001171C092665 |
| Valid from | 2007-12-27 14:37 UTC |
| Valid until | 2010-12-27 14:37 UTC (expired) |
| Signature validity | Not verified |
Engine angr, status timeout, 30 paths explored at a maximum depth of 30. 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.
Based on DriverShield static and dynamic analysis, vbox.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.
vbox.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: cf3a7d4285d65bf8688215407bce1b51d7c6b22497f09021f0fce31cbeb78986.
vbox.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by innotek GmbH.
Related: Other drivers signed by innotek GmbH · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas