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

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

segwindrvx64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver segwindrvx64.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 detections3 / 75
File size65224 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA25665329dad28e92f4bcc64de15c552b6ef424494028b18875b7dba840053bc0cdd
SHA1d702d88b12233be9413446c445f22fda4a92a1d9
MD54ae55080ec8aed49343e40d08370195c

Driver identity

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

File descriptionSEG Windows Driver x64
ProductSEG Windows Driver x64
CompanyInsyde Software Corp.
Original filenamesegwindrvx64.sys
Internal namesegwindrvx64.sys
File version100.00.07.02
CopyrightCopyright (c) 2012 - 2015, Insyde Software Corp. 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 surface54 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (19)

Kernel-mode APIs resolved from the Import Address Table of segwindrvx64.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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwWriteFilemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (18)

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
0x0080BA00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3712
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x00222286mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2209
0x00222141mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2128
0x002222D2mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2228
0x00803B15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3781
0x00800315mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #197
0x00342464mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2329
0x0022D315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1221
0x0022EB15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2757
0x0022C315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #197
0x00225F05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1985
0x003403B8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #238
0xC350A7A8mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2538

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x37900x38006.37CODE, EXEC, READ
page0x7BAC0x7C006.44CODE, EXEC, READ
init0x08E00x0A005.75CODE, EXEC, READ
.rdata0x08AC0x0A004.24IDATA, READ
.data0x07C80x02000.36IDATA, READ, WRITE
.pdata0x03C00x04004.1IDATA, READ
INIT0x042A0x06004.23CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x04180x06002.5IDATA, READ, DISCARD
.reloc0x00140x02000.21IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Insydesoftwarecorp_Segwindrvxsys_Segwindowsdriverx_6532mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - segwindrvx64.sys. Investigate matches in context: expected filenames or stan...
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
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
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
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 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 segwindrvx64.sys

Is segwindrvx64.sys safe?

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

segwindrvx64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 65329dad28e92f4bcc64de15c552b6ef424494028b18875b7dba840053bc0cdd.

What is segwindrvx64.sys?

segwindrvx64.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 CA - G2.

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