ElbyCDIO.sys - Suspicious (33/100) - DriverShield Analysis

Analysis of ElbyCDIO.sys: suspicious verdict, risk score 33/100. 1 YARA match, 3/75 multi-engine detections. SHA256 eea53103e7a5a55d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ElbyCDIO.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ElbyCDIO.sys and assigned a verdict of Suspicious with a composite risk score of 33/100, indicating some risk signals warranting review (30-59 band).

Verdict	Suspicious (33/100)
YARA matches	1
Multi-engine detections	3 / 75
File size	23976 bytes
Code-signing signer	VeriSign Time Stamping Services Signer - G2
Analyzed	2026-09-08
SHA256	eea53103e7a5a55dc1df79797395a2a3e96123ebd71cdd2db4b1be80e7b3f02b
SHA1	3599ea2ac1fa78f423423a4cf90106ea0938dde8
MD5	ae5eb2759305402821aeddc52ba9a6d6

Driver identity

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

File description	ElbyCD Windows NT/2000/XP I/O driver
Product	CDRTools
Company	Elaborate Bytes AG
Original filename	ElbyCDIO.sys
Internal name	ElbyCDIO
File version	6, 0, 2, 0
Copyright	Copyright (C) 2000 - 2009 Elaborate Bytes AG

How the 33/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	5 / 100
Dangerous kernel imports	99 / 100
IOCTL dispatch surface	15 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (22)

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

API	Risk	Why it matters
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwWriteFile	medium	Moderate risk - system modification capability
IoCreateDevice	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign
ExAllocatePool	low	Standard kernel API - generally benign
ProbeForRead	low	Standard kernel API - generally benign
ZwOpenFile	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
ExFreePool	low	Standard kernel API - generally benign
ZwCreateFile	low	Standard kernel API - generally benign
ProbeForWrite	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign

IOCTL dispatch codes (5)

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.

Code	Severity	Transfer	Description
0x0080003E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #15
0x00800016	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #5
0x00803EB4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #4013
0x008016B4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #1453
0x00340474	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #285

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x29F0	0x2A00	6.4	CODE, EXEC, READ
.rdata	0x05C4	0x0600	6.99	IDATA, READ
.data	0x0004	0x0080	0.26	IDATA, READ, WRITE
INIT	0x04A6	0x0500	5.16	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x04D8	0x0500	3.25	IDATA, READ, DISCARD
.reloc	0x018E	0x0200	4.23	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (1)

Rule	Severity	Detects
PUA_VULN_Driver_Elaboratebytesag_Elbycdio_Cdrtools_EEA5	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - elbycdio.sys. Investigate matches in context: expected filenames or standard...

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	VeriSign Time Stamping Services Signer - G2
Signer organisation	VeriSign, Inc.
Issuer	VeriSign Time Stamping Services CA
Serial	3825D7FAF861AF9EF490E726B5D65AD5
Valid from	2007-06-15 00:00 UTC
Valid until	2012-06-14 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: VeriSign Time Stamping Services CA
Chain: GlobalSign Primary Object Publishing CA
Chain: Elaborate Bytes AG
Chain: GlobalSign ObjectSign CA
Chain: GlobalSign Root CA

Symbolic execution

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

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 ElbyCDIO.sys

Is ElbyCDIO.sys safe?

Based on DriverShield static and dynamic analysis, ElbyCDIO.sys shows some suspicious signals and warrants manual review. Its composite risk score is 33/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of ElbyCDIO.sys?

ElbyCDIO.sys has a DriverShield composite risk score of 33/100, placing it in the suspicious verdict band. SHA256: eea53103e7a5a55dc1df79797395a2a3e96123ebd71cdd2db4b1be80e7b3f02b.

What is ElbyCDIO.sys?

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