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

Analysis of RTCore64.sys: vulnerable verdict, risk score 78/100. 1 YARA match, 1/76 multi-engine detections. SHA256 03e0581432f5c8cc. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

RTCore64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver RTCore64.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).

Verdict	Vulnerable (78/100)
YARA matches	1
Multi-engine detections	1 / 76
File size	14648 bytes
Code-signing signer	VeriSign Time Stamping Services Signer - G2
Analyzed	2026-09-06
SHA256	03e0581432f5c8cc727a8aa387f5b69ff84d38d0df6f1226c19c6e960a81e1e9
SHA1	4f376b1d1439477a426ef3c52e8c1c69c2cb5305
MD5	3ecd3ca61ffc54b0d93f8b19161b83da

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	50 / 100
Dangerous kernel imports	78 / 100
IOCTL dispatch surface	3 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	40 / 100

Kernel imports (9)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign

IOCTL dispatch codes (1)

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.

Code	Severity	Transfer	Description
0x00340036	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #13

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x0C74	0x0E00	5.34	CODE, EXEC, READ
.rdata	0x0130	0x0200	2.3	IDATA, READ
.data	0x0058	0x0200	0.63	IDATA, READ, WRITE
.pdata	0x0060	0x0200	0.85	IDATA, READ
INIT	0x0202	0x0400	2.67	CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (1)

Rule	Severity	Detects
VULN_RTCore64	critical	MSI RTCore64.sys

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	VeriSign Time Stamping Services Signer - G2
Signer organisation	VeriSign, Inc.
Issuer	VeriSign Time Stamping Services CA
Serial	3825D7FAF861AF9EF490E726B5D65AD5
Valid from	2007-06-15 00:00 UTC
Valid until	2012-06-14 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: VeriSign Time Stamping Services CA
Chain: GlobalSign Primary Object Publishing CA
Chain: Micro-Star Int'l Co. Ltd.
Chain: GlobalSign ObjectSign CA
Chain: GlobalSign Root CA

Associated CVEs

CVE-2019-16098 - MSI Afterburner RTCore64.sys - arbitrary physical memory read/write via IOCTL

Symbolic execution

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

Is RTCore64.sys safe?

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

RTCore64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 03e0581432f5c8cc727a8aa387f5b69ff84d38d0df6f1226c19c6e960a81e1e9.

What is RTCore64.sys?

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