BSMI.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of BSMI.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 1/75 multi-engine detections. SHA256 59626cac380d8fe0. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

BSMI.sys - Analysis Report

DriverShield analyzed the Windows kernel driver BSMI.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches4
Multi-engine detections1 / 75
File size17056 bytes
Code-signing signerSymantec Time Stamping Services Signer - G3
Analyzed2026-09-06
SHA25659626cac380d8fe0b80a6d4c4406d62ba0683a2f0f68d50ad506ca1b1cf25347
SHA19a35ae9a1f95ce4be64adc604c80079173e4a676
MD5fac8eb49e2fd541b81fcbdeb98a199cb

Driver identity

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

File descriptionSMI Driver
Product4ProductVersion
Company>FileDescription
Original filenameBSMI.sys
Internal nameBSMI.sys
File version1.0.0.3
CopyrightCopyright (C) BIOSTAR Corp. 2011

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

Kernel imports (11)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard 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.

CodeSeverityTransferDescription
0x00222000medium (known exploit)METHOD_BUFFEREDDriver communication init
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00340318mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #198

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x01EC0x02005.23CODE, EXEC, READ
.rdata0x01380x02002.91IDATA, READ
.data0x01100x02000.3IDATA, READ, WRITE
.pdata0x00780x02001.06IDATA, READ
PAGE0x10B70x12005.61CODE, EXEC, READ
INIT0x044A0x06004.34CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03780x04002.88IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Bsmisys_552FmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - BSMIx64.sys. Investigate matches in context: expected filenames or standard ...
PUA_VULN_Driver_Bsmisys_5962mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - BSMI.sys, BSMIXP64.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (10)

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
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services Signer - G3
Signer organisationSymantec Corporation
IssuerVeriSign Time Stamping Services CA
Serial79A2A585F9D1154213D9B83EF6B68DED
Valid from2012-05-01 00:00 UTC
Valid until2012-12-31 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 31 paths explored at a maximum depth of 31. 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 BSMI.sys

Is BSMI.sys safe?

Based on DriverShield static and dynamic analysis, BSMI.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of BSMI.sys?

BSMI.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 59626cac380d8fe0b80a6d4c4406d62ba0683a2f0f68d50ad506ca1b1cf25347.

What is BSMI.sys?

BSMI.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services Signer - G3.

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