cpqsysio64.sys - Vulnerable (72/100) - DriverShield Analysis

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

cpqsysio64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver cpqsysio64.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 matches2
Multi-engine detections0 / 75
File size15168 bytes
Code-signing signerGlobalSign Timestamping CA
Analyzed2026-04-02
SHA2564024b090cebcabaab884c84ec80ffb15622d12632f236383a9b0a470bff9fe33
SHA1e17fa2e3ca1d59e2dd8ddbc1020d77bb3b7156d0
MD5cb7bc352e0a7531faec48de1dbd8a9a1

Driver identity

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

File descriptionPhysical memory driver
ProductPhysical memory driver
CompanyHewlett-Packard
Original filenamecpqsysio.sys
Internal namecpqsysio
File version4.5.0.0
CopyrightCopyright 2004-2009 by Hewlett-Packard Development Company, L.P.

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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface12 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 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 cpqsysio64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemoryhighPotentially 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
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x00340304mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #193
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x098E0x0A005.74CODE, EXEC, READ
.rdata0x01600x02002.17IDATA, READ
.data0x01200x02000.3IDATA, READ, WRITE
.pdata0x00540x02000.76IDATA, READ
INIT0x02920x04003.72CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03680x04002.88IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (9)

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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign Timestamping CA
Signer organisationGlobalSign
IssuerGlobalSign Root CA
Serial400000000012019C19066
Valid from2009-03-18 11:00 UTC
Valid until2028-01-28 12:00 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about cpqsysio64.sys

Is cpqsysio64.sys safe?

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

cpqsysio64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 4024b090cebcabaab884c84ec80ffb15622d12632f236383a9b0a470bff9fe33.

What is cpqsysio64.sys?

cpqsysio64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign Timestamping CA.

Related: Other drivers signed by GlobalSign Timestamping CA · 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