Local kernel code execution via exposed IOCTLs
Published Jan 1, 2022 · Updated Aug 4, 2024
Improper access control in Biostar RACING GT Evo 2.1.1905.1700 allows local users to execute kernel-mode code through driver IOCTLs. BS_RCIO64.sys creates its device with an insufficient DACL; two IOCTLs map attacker-chosen physical memory, while another calls a user-supplied pointer. A low-integrity process that opens the device can read or overwrite physical memory, elevate privileges, or crash Windows without user interaction.
Summary
What happened
Improper access control in Biostar RACING GT Evo 2.1.1905.1700 allows local users to execute kernel-mode code through driver IOCTLs. BS_RCIO64.sys creates its device with an insufficient DACL; two IOCTLs map attacker-chosen physical memory, while another calls a user-supplied pointer. A low-integrity process that opens the device can read or overwrite physical memory, elevate privileges, or crash Windows without user interaction.
The record
- CVE
- CVE-2021-44852
- Published
- Jan 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 1, 2022CVE 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
- BiostarDriverExploit demonstrationproof 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