AppvVemgr.sys - Vulnerable (60/100) - DriverShield Analysis

Analysis of AppvVemgr.sys: vulnerable verdict, risk score 60/100. 1 YARA match, 0/75 multi-engine detections. SHA256 c8bcd77030f948a6. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

AppvVemgr.sys - Analysis Report

DriverShield analyzed the Windows kernel driver AppvVemgr.sys and assigned a verdict of Vulnerable with a composite risk score of 60/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (60/100)
YARA matches1
Multi-engine detections0 / 75
File size218432 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-05-10
SHA256c8bcd77030f948a6287adda728fcba6b4297dec9fe6a05cdeccef624075c8ae1
SHA1a90fb6e87b9a7f2bd39fb6b267cfff4a84259674
MD5633a321028e777f0f5a9f055559f34ea

Driver identity

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

File descriptionMicrosoft Application Virtualization VE Manager Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameAppvVemgr.sys
Internal nameAppvVemgr.sys
File version10.0.26100.1150 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 60/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 matches5 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface78 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (28)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwDeleteKeymediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign

IOCTL dispatch codes (26)

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
0x00809B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1762
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x00809F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2018
0x00343D0BhighMETHOD_NEITHERFILE_DEVICE_DISK Function #3906
0x00220123highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #72
0x0080B58BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3426
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080E9C0mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2672
0x0034B805mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3585
0x0034BE05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3969
0x0034B800mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3584
0x00343DF0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3964
0x00342404mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2305
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00343D41mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3920
0x00343D50mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3924
0x00221FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2042
0x0080938DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1251
0x0034FF81mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #4064
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00800036mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #13

Showing 24 of 26 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1B6F10x1C0006.2CODE, EXEC, READ
fothk0x10000x10000.03CODE, EXEC, READ
.rdata0x83140x90003.86IDATA, READ
.data0x05200x10000.53IDATA, READ, WRITE
.pdata0x0FD80x10005.24IDATA, READ
.idata0x131A0x20003.36IDATA, READ
PAGE0x1A780x20005.62CODE, EXEC, READ
.edata0x00530x10000.17IDATA, READ
INIT0x04CB0x10002.49CODE, EXEC, READ, DISCARD
GFIDS0x010C0x10000.35IDATA, READ, DISCARD
.rsrc0x05180x10001.31IDATA, READ, DISCARD
.reloc0x18780x20004.99IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score90 / 100

YARA rule matches (1)

RuleSeverityDetects
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1071Application Layer ProtocolCommand and Control
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.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000045FF3C96C1A7FF7DA1D00000000045F
Valid from2023-11-16 19:20 UTC
Valid until2024-11-14 19:20 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about AppvVemgr.sys

Is AppvVemgr.sys safe?

Based on DriverShield static and dynamic analysis, AppvVemgr.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 60/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of AppvVemgr.sys?

AppvVemgr.sys has a DriverShield composite risk score of 60/100, placing it in the vulnerable verdict band. SHA256: c8bcd77030f948a6287adda728fcba6b4297dec9fe6a05cdeccef624075c8ae1.

What is AppvVemgr.sys?

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

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