Analysis of rtcore.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 4/75 multi-engine detections. SHA256 01aa278b07b58dc4. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver rtcore.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 | 3 |
| Multi-engine detections | 4 / 75 |
| File size | 14024 bytes |
| Code-signing signer | GlobalSign Timestamping CA - G2 |
| Analyzed | 2026-03-23 |
| SHA256 | 01aa278b07b58dc46c84bd0b1b5c8e9ee4e62ea0bf7a695862444af32e87f1fd |
| SHA1 | f6f11ad2cd2b0cf95ed42324876bee1d83e01775 |
| MD5 | 2d8e4f38b36c334d0a32a7324832501d |
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 | 100 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 3 / 100 |
| Known-vulnerable corpus | 100 / 100 |
| Code-signing state | 0 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of rtcore.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapIoSpace | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| ZwMapViewOfSection | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| HalSetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| HalGetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
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 |
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 | 0x0B64 | 0x0C00 | 5.77 | CODE, EXEC, READ |
| .rdata | 0x012C | 0x0200 | 2.05 | IDATA, READ |
| .data | 0x0058 | 0x0200 | 0.63 | IDATA, READ, WRITE |
| .pdata | 0x0060 | 0x0200 | 0.84 | IDATA, READ |
| INIT | 0x0258 | 0x0400 | 3.07 | CODE, EXEC, READ, WRITE, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Not enabled |
| DEP | Not enabled |
| Integrity check | Not enforced |
| Mitigation score | 20 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| VULN_RTCore64 | critical | MSI RTCore64.sys |
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003 | OS Credential Dumping | Credential Access |
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1006 | Direct Volume Access | Defense Evasion |
| T1014 | Rootkit | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1542.001 | Pre-OS Boot: System Firmware | Persistence |
| T1543.003 | Windows Service | Persistence |
| T1562.001 | Impair Defenses | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1601 | Modify System Image | Defense Evasion |
| T1652 | Device Driver Discovery | Discovery |
| Signer | GlobalSign Timestamping CA - G2 |
|---|---|
| Signer organisation | GlobalSign nv-sa |
| Issuer | GlobalSign Root CA |
| Serial | 400000000012F4EE152D7 |
| Valid from | 2011-04-13 10:00 UTC |
| Valid until | 2028-01-28 12:00 UTC |
| Signature validity | Verified |
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.
Based on DriverShield static and dynamic analysis, rtcore.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.
rtcore.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 01aa278b07b58dc46c84bd0b1b5c8e9ee4e62ea0bf7a695862444af32e87f1fd.
rtcore.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign Timestamping CA - G2.
Related: Other drivers signed by GlobalSign Timestamping 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