Local Windows crash via unvalidated driver IOCTL
Published Feb 5, 2021 · Updated Aug 4, 2024
Improper input validation in Max Secure Max Spyware Detector 1.0.0.044 allows local users to crash Windows via a crafted IOCTL. The MaxProc64.sys driver accepts attacker-controlled values through IOCTL 0x2200019 without validating them before kernel-mode processing. Any local user able to access the driver can trigger a blue-screen crash, interrupting the entire Windows host; other impact remains unspecified.
Summary
What happened
Improper input validation in Max Secure Max Spyware Detector 1.0.0.044 allows local users to crash Windows via a crafted IOCTL. The MaxProc64.sys driver accepts attacker-controlled values through IOCTL 0x2200019 without validating them before kernel-mode processing. Any local user able to access the driver can trigger a blue-screen crash, interrupting the entire Windows host; other impact remains unspecified.
The record
- CVE
- CVE-2020-12122
- Published
- Feb 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 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
- MaxProc64.sys local BSOD proof of conceptproof 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