{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5183 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5183 is a critical memory corruption vulnerability in AMD, published on 25 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-5183 and fix it if it is affected.\n\nWhat it is: CVE-2019-5183 is a critical memory corruption vulnerability in AMD, published on 25 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-5183 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-2019-5183/ (Markdown: https://insights.sbomify.com/CVE-2019-5183/index.md)","id":"CVE-2019-5183","markdown":"https://insights.sbomify.com/CVE-2019-5183/index.md","name":"CVE-2019-5183","record":{"aliases":["GHSA-ppvv-3w29-f4j8"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AMD GPU driver","requires_auth":"none","summary":"A type confusion in the AMD GPU driver allows attackers to execute arbitrary code on the host system via a crafted shader from a virtual machine guest.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"atidxx64","vendor":"amd"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"An exploitable type confusion vulnerability exists in AMD ATIDXX64.DLL driver, versions 26.20.13031.10003, 26.20.13031.15006 and 26.20.13031.18002. A specially crafted pixel shader can cause a type confusion issue, leading to potential code execution. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered from VMware guest, affecting VMware host.","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-2019-5183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Wago","id":"CVE-2019-5184"},"packages":[],"prev":{"headline":"Memory corruption in WAGO PFC200","id":"CVE-2019-5182"},"products":["AMD"],"published":"2020-01-25","related":[{"cvss_score":8.6,"headline":"Denial of service in AMD","id":"CVE-2019-5124","kev_date_added":null,"published":"2020-01-25"},{"cvss_score":8.6,"headline":"Denial of service in AMD","id":"CVE-2019-5146","kev_date_added":null,"published":"2020-01-25"},{"cvss_score":8.6,"headline":"Denial of service in AMD","id":"CVE-2019-5147","kev_date_added":null,"published":"2020-01-25"}],"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 type confusion in the AMD GPU driver allows attackers to execute arbitrary code on the host system via a crafted shader from a virtual machine guest.","url":"https://insights.sbomify.com/CVE-2019-5183/"}