_LSTR_37_nep.sra_10_0.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of _LSTR_37_nep.sra_10_0.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 0/76 multi-engine detections. SHA256 87e791e95d65f3f6. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

_LSTR_37_nep.sra_10_0.sys - Analysis Report

DriverShield analyzed the Windows kernel driver _LSTR_37_nep.sra_10_0.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 detections0 / 76
File size174840 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-08-05
SHA25687e791e95d65f3f6f1f5fd1d62309030822dac3c3d124da820bc692566e84b48
SHA1fca9523c0899ea7e273bca1c5dd3ef5bfb4ca8b7
MD576a57e4861db36240f4e1c0fc84bbd42

Driver identity

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

ProductStormshield Endpoint Security
CompanyStormshield
File version7.2.32.1
CopyrightStormshield - 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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface72 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy80 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (25)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard 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
0x00808B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #738
0x0080BB83highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3808
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00809B8DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1763
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080BB01mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3776
0x003437E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3578
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00808F10mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #964
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0080B389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3298
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0080FE81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4000
0x00802984mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2657
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x002203E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #250
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00803DFEmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #3967
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x00343412mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3332
0x0022010DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #67
0x00220118mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #70
0x00340244mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #145
0x00220068mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #26

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x140FC0x142006.32CODE, EXEC, READ
.fips0x70A30x72006.3CODE, EXEC, READ
.rdata0x75BC0x76007.45IDATA, READ
.data0x08A10x04001.63IDATA, READ, WRITE
.pdata0x16740x18005.05IDATA, READ
PAGE0x064C0x08005.2CODE, EXEC, READ
INIT0x0A360x0C004.82CODE, EXEC, READ, DISCARD
.rsrc0x02A80x04002.27IDATA, READ, DISCARD
.reloc0x00B00x02002.12IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (14)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000003A6AE333708FDA7A7B00000000003A
Valid from2020-03-11 17:31 UTC
Valid until2021-03-05 17:31 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about _LSTR_37_nep.sra_10_0.sys

Is _LSTR_37_nep.sra_10_0.sys safe?

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

_LSTR_37_nep.sra_10_0.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 87e791e95d65f3f6f1f5fd1d62309030822dac3c3d124da820bc692566e84b48.

What is _LSTR_37_nep.sra_10_0.sys?

_LSTR_37_nep.sra_10_0.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · 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