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

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

KslD.sys - Analysis Report

DriverShield analyzed the Windows kernel driver KslD.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 detections1 / 75
File size330112 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-10-07
SHA2562b3195346d9b62b08bb61bb61f0da20b2abb0c726186c09a2e4fa926baacbfc5
SHA1b678371d2dac5ad2fcca014ded25e0cc7a74eed1
MD5b316425d6f200244a25bd7b9998d9c43

Driver identity

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

File descriptionKSLD
ProductMicrosoft Malware Protection
CompanyMicrosoft Corporation
Original filenameKSLD.sys
Internal nameKSLD
File version1.1.25041.64017 (5f4e0875c06cb7d3b67e5e7e4354b254dda9b0b4)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (31)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwReadFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 31 resolved.

IOCTL dispatch codes (39)

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
0x0080B63BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3470
0x0080E903highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2624
0x0080A383highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2272
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x00347263highMETHOD_NEITHERFILE_DEVICE_DISK Function #3224
0x0022011FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #71
0x00220123highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #72
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080BB89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3810
0x0080938DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1251
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0034B941mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3664
0x0034A845mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2577
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x008086B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #430
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00809F21mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1992
0x0080AF89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3042
0x0022358DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3427
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00228FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1018
0x0022BA00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3712
0x0022BA11mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3716

Showing 24 of 39 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3BD6F0x3C0006.32CODE, EXEC, READ
awesome0x00090x04000.1CODE, EXEC, READ
.rdata0xA16C0xA4005.06IDATA, READ
.data0x10F80x04000.55IDATA, READ, WRITE
.pdata0x2C700x30005.19IDATA, READ
PAGE0x05470x08004.67CODE, EXEC, READ
INIT0x15160x18005.74CODE, EXEC, READ, DISCARD
.rsrc0x04480x08002.1IDATA, READ, DISCARD
.reloc0x18180x1C006.11IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score90 / 100

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Microsoftcorporation_Ksld_Microsoftmalwareprotection_2B31mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - KslD.sys, MpKslDrv.sys. Investigate matches in context: expected filenames o...
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (19)

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

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial33000004A882E6B8AC1C5D5FF00000000004A8
Valid from2024-09-12 20:04 UTC
Valid until2025-09-11 20:04 UTC (expired)
Signature validityNot verified

Symbolic execution

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

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

Is KslD.sys safe?

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

KslD.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 2b3195346d9b62b08bb61bb61f0da20b2abb0c726186c09a2e4fa926baacbfc5.

What is KslD.sys?

KslD.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact