cpuz-1.0.4.1.sys - Vulnerable (72/100) - DriverShield Analysis

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

cpuz-1.0.4.1.sys - Analysis Report

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

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections2 / 75
File size46400 bytes
Code-signing signerVeriSign Class 3 Public Primary Certification Authority - G5
Analyzed2026-09-06
SHA256ded2927f9a4e64eefd09d0caba78e94f309e3a6292841ae81d5528cab109f95d
SHA1f5696fb352a3fbd14fb1a89ad21a71776027f9ab
MD5db72def618cbc3c5f9aa82f091b54250

Driver identity

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

File descriptionCPUID Driver
ProductCPUID service
CompanyCPUID
Original filenamecpuz.sys
Internal namecpuz.sys
File version6.1.7600.16385 built by: WinDDK
CopyrightCopyright(C) 2016 CPUID

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

Kernel imports (17)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x9C402500mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2368
0x0080B389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3298
0x0080BB89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3810
0x00340031mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #12
0x003402F0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #188
0x008002A2mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #168

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3A060x3C006.1CODE, EXEC, READ
.rdata0x048C0x06003.39IDATA, READ
.data0x04400x02000.38IDATA, READ, WRITE
.pdata0x00F00x02001.95IDATA, READ
INIT0x040E0x06003.88CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03500x04002.92IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Cpuid_Cpuzsys_Cpuidservice_0E85mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - cpuz.sys. Investigate matches in context: expected filenames or standard ven...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (15)

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
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Class 3 Public Primary Certification Authority - G5
Signer organisationVeriSign, Inc.
Serial250CE8E030612E9F2B89F7054D7CF8FD
Valid from2006-11-08 00:00 UTC
Valid until2021-11-07 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Is cpuz-1.0.4.1.sys safe?

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

What is the risk score of cpuz-1.0.4.1.sys?

cpuz-1.0.4.1.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: ded2927f9a4e64eefd09d0caba78e94f309e3a6292841ae81d5528cab109f95d.

What is cpuz-1.0.4.1.sys?

cpuz-1.0.4.1.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 Class 3 Public Primary Certification Authority - G5.

Related: Other drivers signed by VeriSign Class 3 Public Primary Certification Authority - G5 · 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