{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44852 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44852 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44852 is a high-severity vulnerability in n/a, published on 1 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44852 and fix it if it is affected.\n\nWhat it is: CVE-2021-44852 is a high-severity vulnerability in n/a, published on 1 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-44852 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-2021-44852/ (Markdown: https://insights.sbomify.com/CVE-2021-44852/index.md)","id":"CVE-2021-44852","markdown":"https://insights.sbomify.com/CVE-2021-44852/index.md","name":"CVE-2021-44852","record":{"aliases":["GHSA-rgp2-m7fc-79r8"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Biostar motherboard driver","requires_auth":"low_privilege","summary":"A low-integrity process can exploit the Biostar RACING GT Evo driver to read/write arbitrary physical memory, enabling arbitrary code execution and privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"racing_gt_evo","vendor":"biostar"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in BS_RCIO64.sys in Biostar RACING GT Evo 2.1.1905.1700. A low-integrity process can open the driver's device object and issue IOCTLs to read or write to arbitrary physical memory locations (or call an arbitrary address), leading to execution of arbitrary code. This is associated with 0x226040, 0x226044, and 0x226000.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-03-22","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-03-22T04:47:54Z","kind":"github_poc","ref":"https://github.com/CrackerCat/CVE-2021-44852","stars":2,"title":"An issue was discovered in BS_RCIO64.sys in Biostar RACING GT Evo 2.1.1905.1700. A low-integrity process can open the driver's device object and issue IOCTLs to read or write to arbitrary physical memory locations (or call an arbitrary address), leading to execution of arbitrary code. This is associated with 0x226040, 0x226044, and 0x226000."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2021-44852","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2021-44854"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-44850"},"products":["n/a"],"published":"2022-01-01","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A low-integrity process can exploit the Biostar RACING GT Evo driver to read/write arbitrary physical memory, enabling arbitrary code execution and privilege escalation.","url":"https://insights.sbomify.com/CVE-2021-44852/"}