{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-10709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10709 is a high-severity vulnerability in n/a, published on 30 Oct 2018. 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-2018-10709 and fix it if it is affected.\n\nWhat it is: CVE-2018-10709 is a high-severity vulnerability in n/a, published on 30 Oct 2018. 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-2018-10709 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-2018-10709/ (Markdown: https://insights.sbomify.com/CVE-2018-10709/index.md)","id":"CVE-2018-10709","markdown":"https://insights.sbomify.com/CVE-2018-10709/index.md","name":"CVE-2018-10709","record":{"aliases":["GHSA-v8wr-25mj-7jf2"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ASRock RGB LED driver","requires_auth":"low_privilege","summary":"Local attackers can exploit exposed driver functionality to read/write CR registers, leading to privilege escalation and arbitrary code execution.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"a-tuning","vendor":"asrock"},{"product":"f-stream","vendor":"asrock"},{"product":"restart_to_uefi","vendor":"asrock"},{"product":"rgbled","vendor":"asrock"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to read and write CR register values. This could be leveraged in a number of ways to ultimately run code with elevated privileges.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-10-29","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-10-29","kind":"exploitdb","ref":"45716","stars":null,"title":"ASRock Drivers - Privilege Escalation"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2018-10709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2018-10710"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2018-10706"},"products":["n/a"],"published":"2018-10-30","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-10711","kev_date_added":null,"published":"2018-10-30"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-10712","kev_date_added":null,"published":"2018-10-30"},{"cvss_score":7.1,"headline":"Privilege escalation in n/a","id":"CVE-2018-10710","kev_date_added":null,"published":"2018-10-30"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can exploit exposed driver functionality to read/write CR registers, leading to privilege escalation and arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2018-10709/"}