Dbgv.sys - Clean (23/100) - DriverShield Analysis

Analysis of Dbgv.sys: clean verdict, risk score 23/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 077ca411c27bcdde. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

Dbgv.sys - Analysis Report

DriverShield analyzed the Windows kernel driver Dbgv.sys and assigned a verdict of Clean with a composite risk score of 23/100, indicating no notable risk signals (0-29 band).

VerdictClean (23/100)
YARA matches0
Multi-engine detections0 / 76
File size23392 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-03-23
SHA256077ca411c27bcdde28ea7247f69ca9162f63574feae994a356e70052690f17f8
SHA10a3f0cbd836b0576a03ee63d5ec4b21a37f6d012
MD5fb9dae94030d4e62f4ab8d039e30af94

Driver identity

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

File descriptionWindows Debug Monitor
ProductSysinternals DebugView
CompanySysinternals
Original filenamedbgv.Sys
Internal namedbgv.sys
File version4.75
CopyrightCopyright (C) M. Russinovich 1998-2008

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

Kernel imports (13)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (3)

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
0x0034DB0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1731
0x00347B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3779
0x003402FCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #191

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1FA50x20006.08CODE, EXEC, READ
.rdata0x071C0x08003.81IDATA, READ
.data0x14480x02001.22IDATA, READ, WRITE
.pdata0x01E00x02003.73IDATA, READ
INIT0x04F60x06004.46CODE, EXEC, READ, DISCARD
.rsrc0x03600x04002.85IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score60 / 100

MITRE ATT&CK techniques (9)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial330000009484C47568579AAFE9000000000094
Valid from2020-03-04 19:12 UTC
Valid until2021-03-03 19:12 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about Dbgv.sys

Is Dbgv.sys safe?

Based on DriverShield static and dynamic analysis, Dbgv.sys is assessed as clean, with no notable risk signals. Its composite risk score is 23/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of Dbgv.sys?

Dbgv.sys has a DriverShield composite risk score of 23/100, placing it in the clean verdict band. SHA256: 077ca411c27bcdde28ea7247f69ca9162f63574feae994a356e70052690f17f8.

What is Dbgv.sys?

Dbgv.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact