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

Analysis of HwOs2Ec.sys: vulnerable verdict, risk score 60/100. 2 YARA matches, 2/75 multi-engine detections. SHA256 b179e1ab6dc0b1ae. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

HwOs2Ec.sys - Analysis Report

DriverShield analyzed the Windows kernel driver HwOs2Ec.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 matches2
Multi-engine detections2 / 75
File size42104 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA256b179e1ab6dc0b1aee783adbcad4ad6bb75a8a64cb798f30c0dd2ee8aaf43e6de
SHA126c4a7b392d7e7bd7f0a2a758534e45c0d9a56ab
MD5bae1f127c4ff21d8fe45e2bbfc59c180

Driver identity

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

File descriptionHwOs2Ec
ProductHuawei MateBook
CompanyHuawei
Original filenameHwOs2Ec.sys
Internal nameHwOs2Ec
File version1.0.0.1
CopyrightCopyright (C) 2016

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 matches10 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface18 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (25)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign

IOCTL dispatch codes (6)

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
0x008045C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #369
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00343B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3779
0x00224014mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #5
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x003402A4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #169

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x20840x22006.08CODE, EXEC, READ
.rdata0x09940x0A004.23IDATA, READ
.data0x061C0x02000.3IDATA, READ, WRITE
.pdata0x033C0x04003.57IDATA, READ
.gfids0x00040x02000.02IDATA, READ
PAGE0x18EA0x1A006.09CODE, EXEC, READ
INIT0x092A0x0A005.21CODE, EXEC, READ, DISCARD
.rsrc0x03080x04002.59IDATA, READ, DISCARD
.reloc0x00140x02000.22IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Huawei_Hwosec_Huaweimatebook_B179mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - HwOs2Ec7x64.sys. Investigate matches in context: expected filenames or stand...
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
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
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Is HwOs2Ec.sys safe?

Based on DriverShield static and dynamic analysis, HwOs2Ec.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 HwOs2Ec.sys?

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

What is HwOs2Ec.sys?

HwOs2Ec.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - 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