Local kernel code execution via unchecked IOCTL copy
Published Aug 5, 2022 · Updated Aug 3, 2024
Stack-based buffer overflow in Uniwill SparkIO.sys 1.0 allows local users to execute code in the kernel via IOCTL 0x40002008. The IOCTL dispatcher copies a caller-controlled input length into a 32-byte kernel-stack buffer without enforcing an upper bound. Opening the \.\SparkIO device locally is required; overwriting the saved return address enables kernel code execution or crashes the Windows kernel.
Summary
What happened
Stack-based buffer overflow in Uniwill SparkIO.sys 1.0 allows local users to execute code in the kernel via IOCTL 0x40002008. The IOCTL dispatcher copies a caller-controlled input length into a 32-byte kernel-stack buffer without enforcing an upper bound. Opening the \.\SparkIO device locally is required; overwriting the saved return address enables kernel code execution or crashes the Windows kernel.
The record
- CVE
- CVE-2022-37415
- Published
- Aug 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Uniwill SparkIO.sys PoCproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo