Local system crash via unchecked Type3 pointer
Published Feb 16, 2021 · Updated Aug 3, 2024
Denial of service in Dekart Private Disk 2.15 allows local users to crash Windows via a crafted IOCTL request to its kernel driver. The driver reads an eight-byte flag through the Type3 input pointer before validating a METHOD_NEITHER request, so invalid or unpaged memory is dereferenced. Low-privilege local code can trigger a kernel page fault and blue-screen the host; no data disclosure or modification is reported.
Summary
What happened
Denial of service in Dekart Private Disk 2.15 allows local users to crash Windows via a crafted IOCTL request to its kernel driver. The driver reads an eight-byte flag through the Type3 input pointer before validating a METHOD_NEITHER request, so invalid or unpaged memory is dereferenced. Low-privilege local code can trigger a kernel page fault and blue-screen the host; no data disclosure or modification is reported.
The record
- CVE
- CVE-2021-27203
- Published
- Feb 16, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 16, 2021CVE 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.
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
- Rootshell Private Disk denial-of-service 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