{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-6101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-6101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-6101 is a critical memory corruption vulnerability in AMD, published on 20 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-6101 and fix it if it is affected.\n\nWhat it is: CVE-2020-6101 is a critical memory corruption vulnerability in AMD, published on 20 Jul 2020. 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-6101 in the wild and no public exploit code.\n\nAffected product: AMD. 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-6101/ (Markdown: https://insights.sbomify.com/CVE-2020-6101/index.md)","id":"CVE-2020-6101","markdown":"https://insights.sbomify.com/CVE-2020-6101/index.md","name":"CVE-2020-6101","record":{"aliases":["GHSA-3583-6263-6c39"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"AMD Radeon DirectX Driver","requires_auth":"low_privilege","summary":"A memory corruption vulnerability in the AMD Radeon DirectX 11 driver allows attackers to execute arbitrary code on the Hyper-V host via a crafted shader file.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"radeon_directx_11_driver_atidxx64.dll","vendor":"amd"}],"cvss":{"score":9.9,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.dll 26.20.15019.19000. An attacker can provide a specially crafted shader file to trigger this vulnerability, resulting in code execution. This vulnerability can be triggered from a HYPER-V guest using the RemoteFX feature, leading to executing the vulnerable code on the HYPER-V host (inside of the rdvgm.exe process). Theoretically this vulnerability could be also triggered from web browser (using webGL and webassembly).","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":"Memory corruption in AMD","id":"CVE-2020-6101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in AMD","id":"CVE-2020-6102"},"packages":[],"prev":{"headline":"Memory corruption in AMD","id":"CVE-2020-6100"},"products":["AMD"],"published":"2020-07-20","related":[{"cvss_score":9.9,"headline":"Memory corruption in AMD","id":"CVE-2020-6100","kev_date_added":null,"published":"2020-07-20"},{"cvss_score":9.9,"headline":"Memory corruption in AMD","id":"CVE-2020-6102","kev_date_added":null,"published":"2020-07-20"},{"cvss_score":9.9,"headline":"Memory corruption in AMD","id":"CVE-2020-6103","kev_date_added":null,"published":"2020-07-20"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A memory corruption vulnerability in the AMD Radeon DirectX 11 driver allows attackers to execute arbitrary code on the Hyper-V host via a crafted shader file.","url":"https://insights.sbomify.com/CVE-2020-6101/"}