TeliGevDriver.sys - Clean (23/100) - DriverShield Analysis

Analysis of TeliGevDriver.sys: clean verdict, risk score 23/100. 0 YARA matches. SHA256 0b57ed1d84bf9772. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

TeliGevDriver.sys - Analysis Report

DriverShield analyzed the Windows kernel driver TeliGevDriver.sys and assigned a verdict of Clean with a composite risk score of 23/100, indicating no notable risk signals (0-29 band).

VerdictClean (23/100)
YARA matches0
File size85568 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-07-09
SHA2560b57ed1d84bf977254ae907b8a9f14cdeb7f3c200c9837306451ebcbc2a0e232
SHA17be6a31ae29f8e9106589d41b3fed277927b848f
MD58e73b99366434669305cbc66fdce1ef3

Driver identity

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

File descriptionTeli GigE Vision Compliant Filter Driver
ProductTeliGevDriver
CompanyTOSHIBA TELI CORPORATION
Original filenameTeliGevDriver
Internal nameTeliGevDriver
File version2.0.12.1
CopyrightCopyright (C) 2013 TOSHIBA TELI CORPORATION. All rights reserved.

How the 23/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 matches0 / 100
Dangerous kernel imports90 / 100
IOCTL dispatch surface54 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeSetEventlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryValueKeylowStandard 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
0x00802840mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2576
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0080838DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #227
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00222028mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2058
0x00808315mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #197
0x00805315mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1221
0x0080AB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2757
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00348715mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #453
0x0080A38DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2275
0x00808B8DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #739
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x003403B0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #236

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xF4370xF6006.28CODE, EXEC, READ
.rdata0x18DC0x1A004.7IDATA, READ
.data0x094C0x02000.81IDATA, READ, WRITE
.pdata0x0AEC0x0C004.59IDATA, READ
.gfids0x00040x02000.04IDATA, READ
INIT0x0F840x10005.5CODE, EXEC, READ, DISCARD
.rsrc0x04100x06002.49IDATA, READ, DISCARD
.reloc0x002C0x02000.56IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about TeliGevDriver.sys

Is TeliGevDriver.sys safe?

Based on DriverShield static and dynamic analysis, TeliGevDriver.sys is assessed as clean, with no notable risk signals. Its composite risk score is 23/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of TeliGevDriver.sys?

TeliGevDriver.sys has a DriverShield composite risk score of 23/100, placing it in the clean verdict band. SHA256: 0b57ed1d84bf977254ae907b8a9f14cdeb7f3c200c9837306451ebcbc2a0e232.

What is TeliGevDriver.sys?

TeliGevDriver.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact