{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10234 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10234 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10234 is a medium-severity vulnerability in n/a, published on 5 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10234 and fix it if it is affected.\n\nWhat it is: CVE-2020-10234 is a medium-severity vulnerability in n/a, published on 5 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-10234 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-10234/ (Markdown: https://insights.sbomify.com/CVE-2020-10234/index.md)","id":"CVE-2020-10234","markdown":"https://insights.sbomify.com/CVE-2020-10234/index.md","name":"CVE-2020-10234","record":{"aliases":["GHSA-pr3w-2ff8-48mm"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Windows kernel driver","requires_auth":"low_privilege","summary":"An unprivileged user can cause a system crash by sending a specific IOCTL to the IObit Advanced SystemCare kernel driver.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"advanced_systemcare","vendor":"iobit"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Null dereference in n/a","id":"CVE-2020-10234","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Froxlor arbitrary code execution via the database configuration options","id":"CVE-2020-10235"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-10233"},"products":["n/a"],"published":"2021-02-05","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-16711","kev_date_added":null,"published":"2018-09-26"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-24138","kev_date_added":null,"published":"2022-07-06"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2021-44968","kev_date_added":null,"published":"2022-02-18"},{"cvss_score":7.1,"headline":"Path traversal in n/a","id":"CVE-2020-14990","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2018-16712","kev_date_added":null,"published":"2018-09-26"},{"cvss_score":6.5,"headline":"Privilege escalation in n/a","id":"CVE-2018-16713","kev_date_added":null,"published":"2018-09-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An unprivileged user can cause a system crash by sending a specific IOCTL to the IObit Advanced SystemCare kernel driver.","url":"https://insights.sbomify.com/CVE-2020-10234/"}