DBUtil_2_3.sys - Malicious (88/100) - DriverShield Analysis

Analysis of DBUtil_2_3.sys: malicious verdict, risk score 88/100. 3 YARA matches, 8/76 multi-engine detections. SHA256 0296e2ce999e67c7. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

DBUtil_2_3.sys - Analysis Report

DriverShield analyzed the Windows kernel driver DBUtil_2_3.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches3
Multi-engine detections8 / 76
File size14840 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-03-23
SHA2560296e2ce999e67c76352613a718e11516fe1b0efc3ffdb8918fc999dd76a73a5
SHA1c948ae14761095e4d76b55d9de86412258be7afd
MD5c996d7971c49252c582171d9380360f2

How the 88/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface6 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference40 / 100

Kernel imports (10)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
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
MmUnmapIoSpacemediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (2)

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
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0CBE0x0E005.85CODE, EXEC, READ
.rdata0x01DC0x02004.32IDATA, READ
.data0x01700x02001.5IDATA, READ, WRITE
.pdata0x00900x02001.27IDATA, READ
PAGE0x032C0x04005.16CODE, EXEC, READ
INIT0x02960x04003.62CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
VULN_DBUtilcriticalDell dbutil_2_3.sys CVE-2021-21551
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (10)

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
T1543.003Windows ServicePersistence
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Associated CVEs

Symbolic execution

Engine angr, status completed, 76 paths explored at a maximum depth of 76. 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.

Frequently asked questions about DBUtil_2_3.sys

Is DBUtil_2_3.sys safe?

Based on DriverShield static and dynamic analysis, DBUtil_2_3.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of DBUtil_2_3.sys?

DBUtil_2_3.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 0296e2ce999e67c76352613a718e11516fe1b0efc3ffdb8918fc999dd76a73a5.

What is DBUtil_2_3.sys?

DBUtil_2_3.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 · CVE-2021-21551 · 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