{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-15368 exists.","fix":"No fix has been published for CVE-2020-15368 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15368 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. 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-2020-15368 and fix it if it is affected.\n\nWhat it is: CVE-2020-15368 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-15368 exists.\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-15368/ (Markdown: https://insights.sbomify.com/CVE-2020-15368/index.md)","id":"CVE-2020-15368","markdown":"https://insights.sbomify.com/CVE-2020-15368/index.md","name":"CVE-2020-15368","record":{"aliases":["GHSA-7387-h76h-9m29"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ASRock RGB Driver","requires_auth":"low_privilege","summary":"A local attacker can exploit improper access restrictions in the ASRock RGB Driver to trigger a system crash or escalate privileges.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rgb_driver_firmware","vendor":"asrock"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering a triple fault via a request to zero CR3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-06-29","github_poc":3,"max_poc_stars":516,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-06-29T04:38:24Z","kind":"github_poc","ref":"https://github.com/stong/CVE-2020-15368","stars":516,"title":"CVE-2020-15368, aka \"How to exploit a vulnerable driver\""},{"date":"2024-08-10T23:51:38Z","kind":"github_poc","ref":"https://github.com/R7flex/asrockploit","stars":8,"title":"arbitrary code execution with CVE-2020-15368"},{"date":"2026-09-23T16:14:39Z","kind":"github_poc","ref":"https://github.com/egorrsp/CVE-2020-15368-AsrDrv103-research","stars":7,"title":"Reverse engineering research of ASRock AsrDrv103.sys (CVE-2020-15368), covering its driver interface, encrypted request protocol, and privileged hardware access primitives."}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2020-15368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Brocade Fabric OS","id":"CVE-2020-15369"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-15367"},"products":["n/a"],"published":"2020-06-29","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["n/a"]},"summary":"A local attacker can exploit improper access restrictions in the ASRock RGB Driver to trigger a system crash or escalate privileges.","url":"https://insights.sbomify.com/CVE-2020-15368/"}