OemHwUpd.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of OemHwUpd.sys: vulnerable verdict, risk score 78/100. 2 YARA matches, 15/76 multi-engine detections. SHA256 3111f4d7d4fac551. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

OemHwUpd.sys - Analysis Report

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

VerdictVulnerable (78/100)
YARA matches2
Multi-engine detections15 / 76
File size66112 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-03-24
SHA2563111f4d7d4fac55103453c4c8adb742def007b96b7c8ed265347df97137fbee0
SHA1d39a79ccfa41ec4a2c4cb9073721e299eee778ad
MD56aa2ed7241d3f00d75baf68572e0ed7b

Driver identity

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

File descriptionEnCase Driver
ProductEnCase Driver
CompanyGuidance Software Inc.
Original filenameEnPortv.sys
Internal nameEnPortv.sys
CopyrightCopyright (C) Guidance Software, Inc.2005-2006

How the 78/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 surface45 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (26)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
KeAttachProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetInformationFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign

IOCTL dispatch codes (15)

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
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0034FF81mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #4064
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x00223048mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3090
0x0022309CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3111
0x00347F0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #4035
0x00225DE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1914
0x00222DE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2938
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00223411mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3332
0x00340304mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #193

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xC9DC0xCA006.31CODE, EXEC, READ
.rdata0x06BC0x08004.19IDATA, READ
.data0x05C00x02000.3IDATA, READ, WRITE
.pdata0x02700x04002.87IDATA, READ
INIT0x06600x08004.46CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03680x04002.88IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_ProcKillcriticalProcess termination EDR killer
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
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
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

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. 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 OemHwUpd.sys

Is OemHwUpd.sys safe?

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

What is the risk score of OemHwUpd.sys?

OemHwUpd.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 3111f4d7d4fac55103453c4c8adb742def007b96b7c8ed265347df97137fbee0.

What is OemHwUpd.sys?

OemHwUpd.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