CAD.sys - Clean (23/100) - DriverShield Analysis

Analysis of CAD.sys: clean verdict, risk score 23/100. 0 YARA matches. SHA256 cdbd820b6d383ec0. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

CAD.sys - Analysis Report

DriverShield analyzed the Windows kernel driver CAD.sys and assigned a verdict of Clean with a composite risk score of 23/100, indicating no notable risk signals (0-29 band).

VerdictClean (23/100)
YARA matches0
File size66576 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256cdbd820b6d383ec0a8151ea4300435c2bad085ec55db185c5e16caf961443888
SHA1625ecd141d98d2fb74d7dc7ffe7ea142bfe475f5
MD5e7690568d2a5fa3d4e6d28b42358a122

Driver identity

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

File descriptionCharge Arbiration Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamecad.sys
Internal namecad.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 23/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 matches0 / 100
Dangerous kernel imports51 / 100
IOCTL dispatch surface72 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (10)

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

APIRiskWhy it matters
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwOpenFilelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (24)

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
0x00800127highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #73
0x00800083highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #32
0x00800047highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #17
0x0022011BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #70
0x0080838BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #226
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x00347F83highMETHOD_NEITHERFILE_DEVICE_DISK Function #4064
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080858DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #355
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8
0x0080005CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #23
0x0080005DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #23
0x0080003DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #15
0x0022012CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #75
0x00220118mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #70
0x0022641AmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2310
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0080FE81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4000
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00228341mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #208
0x00808B48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #722
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00340380mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #224

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x12A90x14005.65CODE, EXEC, READ
.rdata0x3A080x3C005IDATA, READ
.data0x04400x02001.28IDATA, READ, WRITE
.pdata0x048C0x06003.6IDATA, READ
.idata0x06BC0x08003.95IDATA, READ
PAGE0x6F9E0x70006.12CODE, EXEC, READ
INIT0x01220x02003.92CODE, EXEC, READ, DISCARD
GFIDS0x00600x02000.88IDATA, READ, DISCARD
.rsrc0x05A00x06003.08IDATA, READ, DISCARD
.reloc0x035C0x04005.08IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002System Services: Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about CAD.sys

Is CAD.sys safe?

Based on DriverShield static and dynamic analysis, CAD.sys is assessed as clean, with no notable risk signals. Its composite risk score is 23/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of CAD.sys?

CAD.sys has a DriverShield composite risk score of 23/100, placing it in the clean verdict band. SHA256: cdbd820b6d383ec0a8151ea4300435c2bad085ec55db185c5e16caf961443888.

What is CAD.sys?

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

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact