Kernel code execution via unchecked IOCTL copy length
Published Dec 7, 2021 · Updated Aug 4, 2024
Buffer overflow in FlexiHub for Windows allows local users to execute kernel code or crash Windows through a crafted I/O request. IOCTL 0x22001B allocates a kernel buffer using one attacker-controlled length, then passes a larger, independently controlled length to memmove. Any local user able to open the unprotected driver device can corrupt kernel memory, yielding elevation to kernel privileges or a system crash.
Summary
What happened
Buffer overflow in FlexiHub for Windows allows local users to execute kernel code or crash Windows through a crafted I/O request. IOCTL 0x22001B allocates a kernel buffer using one attacker-controlled length, then passes a larger, independently controlled length to memmove. Any local user able to open the unprotected driver device can corrupt kernel memory, yielding elevation to kernel privileges or a system crash.
The record
- CVE
- CVE-2021-42990
- Published
- Dec 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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.
Weakness, pattern, technique
Public exploit references
- IOCTL 0x22001B BSoD proof of conceptproof of concept · demonstrated
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