CVE-2020-10234
First published: Fri Feb 05 2021(Updated: )
The AscRegistryFilter.sys kernel driver in IObit Advanced SystemCare 13.2 allows an unprivileged user to send an IOCTL to the device driver. If the user provides a NULL entry for the dwIoControlCode parameter, a kernel panic (aka BSOD) follows. The IOCTL codes can be found in the dispatch function: 0x8001E000, 0x8001E004, 0x8001E008, 0x8001E00C, 0x8001E010, 0x8001E014, 0x8001E020, 0x8001E024, 0x8001E040, 0x8001E044, and 0x8001E048. \DosDevices\AscRegistryFilter and \Device\AscRegistryFilter are affected.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Iobit Advanced Systemcare | =13.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2020-10234?
CVE-2020-10234 is a vulnerability in the AscRegistryFilter.sys kernel driver in IObit Advanced SystemCare 13.2 that allows an unprivileged user to send a malicious IOCTL to the driver, resulting in a kernel panic (BSOD).
How does CVE-2020-10234 affect IObit Advanced SystemCare?
CVE-2020-10234 affects the AscRegistryFilter.sys kernel driver in IObit Advanced SystemCare 13.2, allowing an unprivileged user to trigger a kernel panic by sending a specific IOCTL to the driver.
What is the severity of CVE-2020-10234?
The severity of CVE-2020-10234 is rated as medium with a CVSS score of 6.5.
How can I fix CVE-2020-10234?
To fix CVE-2020-10234, it is recommended to update IObit Advanced SystemCare to a version that includes a patch for the vulnerability.
Where can I find more information about CVE-2020-10234?
More information about CVE-2020-10234 can be found at the following references: [link1], [link2], [link3].
- collector/nvd-index
- vendor/iobit
- canonical/iobit advanced systemcare
- version/iobit advanced systemcare/13.2