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

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

sandra_x64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver sandra_x64.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 detections0 / 75
File size23112 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-09-06
SHA2560eab16c7f54b61620277977f8c332737081a46bc6bbde50742b6904bdd54f502
SHA12fe874274bac6842819c1e9fe9477e6d5240944d
MD55efbbfcc6adac121c8e2fe76641ed329

Driver identity

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

File descriptionSandra Device Driver (x64)(Unicode)
ProductSiSoftware Sandra
CompanySiSoftware
Original filenameSANDRA
Internal nameSANDRA
File version15.18.1.1 built by: WinDDK
CopyrightCopyright © SiSoftware Ltd 1995-Present. 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 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 (15)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard 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
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00229715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1477
0x00228715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #453
0x00227B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3781
0x00221315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1221
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00340360mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #216

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x234E0x24006.28CODE, EXEC, READ
.rdata0x030C0x04003.55IDATA, READ
.data0x01B40x02000.3IDATA, READ, WRITE
.pdata0x01500x02002.8IDATA, READ
INIT0x09620x0A005.55CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x07200x08003.12IDATA, 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_Sisoftware_Sandra_Sisoftwaresandra_0EABmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - sandra.sys. Investigate matches in context: expected filenames or standard v...
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
T1112Modify RegistryDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. 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 sandra_x64.sys

Is sandra_x64.sys safe?

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

sandra_x64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 0eab16c7f54b61620277977f8c332737081a46bc6bbde50742b6904bdd54f502.

What is sandra_x64.sys?

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

Related: Other drivers signed by VeriSign Time Stamping Services Signer - G2 · 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