Analysis of Cormem.sys: malicious verdict, risk score 88/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 40c855d20d497823. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver Cormem.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).
| Verdict | Malicious (88/100) |
| YARA matches | 0 |
| Multi-engine detections | 0 / 76 |
| File size | 77616 bytes |
| Code-signing signer | DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 |
| Analyzed | 2026-03-24 |
| SHA256 | 40c855d20d497823716a08a443dc85846233226985ee653770bc3b245cf2ed0f |
| SHA1 | bceae6dc87c9c6c33555a4a9008be14c66fd1e20 |
| MD5 | 78fb9882e498d964f42169ce511f07fc |
Version resource data embedded in the Cormem.sys PE header, as extracted by the analysis engine.
| File description | Sapera Memory Manager |
|---|---|
| Product | Sapera LT |
| Company | Teledyne Digital Imaging Inc. |
| Original filename | CorMem.sys |
| Internal name | CorMem.sys |
| File version | 9.00 |
| Copyright | Copyright (c) Teledyne Digital Imaging Inc.1997-2024 |
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 | 0 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 100 / 100 |
| Known-vulnerable corpus | 0 / 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 Cormem.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapLockedPagesSpecifyCache | 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 |
| MmGetPhysicalAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmAllocateContiguousMemory | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| IoGetDeviceObjectPointer | medium | Moderate risk - system modification capability |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| IoBuildDeviceIoControlRequest | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| IoCreateDevice | 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 |
|---|---|---|---|
| 0x0022201C | critical (known exploit) | METHOD_BUFFERED | Process termination by PID (wsftprm) |
| 0x00222000 | medium (known exploit) | METHOD_BUFFERED | Driver communication init |
| 0x00343677 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #3485 |
| 0x00220123 | high | METHOD_NEITHER | FILE_DEVICE_UNKNOWN Function #72 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x0080048C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #291 |
| 0x0022200C | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2051 |
| 0x0080163D | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #1423 |
| 0x0022B941 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3664 |
| 0x0034730D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #3267 |
| 0x00349B0D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #1731 |
| 0x0034BF0D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #4035 |
| 0x0034C30D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #195 |
| 0x0034DF0D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #1987 |
| 0x00221F25 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #1993 |
| 0x0080BF41 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #4048 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x00341715 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #1477 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x00340324 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #201 |
| 0x00340032 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #12 |
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 | 0x9059 | 0x9200 | 6.5 | CODE, EXEC, READ |
| .rdata | 0x0A60 | 0x0C00 | 4.19 | IDATA, READ |
| .data | 0x01B0 | 0x0200 | 0.45 | IDATA, READ, WRITE |
| .pdata | 0x0408 | 0x0600 | 3.18 | IDATA, READ |
| NONPAGE | 0x21C0 | 0x2200 | 0.01 | IDATA, READ, WRITE |
| .gfids | 0x0004 | 0x0200 | 0.02 | IDATA, READ |
| INIT | 0x0632 | 0x0800 | 4.49 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x0410 | 0x0600 | 2.56 | IDATA, READ, DISCARD |
| .reloc | 0x0030 | 0x0200 | 0.46 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 70 / 100 |
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 |
| T1112 | Modify Registry | Defense Evasion |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 |
|---|---|
| Signer organisation | DigiCert, Inc. |
| Issuer | DigiCert Trusted Root G4 |
| Serial | 8AD40B260D29C4C9F5ECDA9BD93AED9 |
| Valid from | 2021-04-29 00:00 UTC |
| Valid until | 2036-04-28 23:59 UTC |
| Signature validity | Verified |
Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, Cormem.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.
Cormem.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 40c855d20d497823716a08a443dc85846233226985ee653770bc3b245cf2ed0f.
Cormem.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