{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-8809 exists.","fix":"No fix has been published for CVE-2016-8809 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8809 is a high-severity vulnerability in Nvidia Gpu Driver, published on 8 Nov 2016. 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-2016-8809 and fix it if it is affected.\n\nWhat it is: CVE-2016-8809 is a high-severity vulnerability in Nvidia Gpu Driver, published on 8 Nov 2016. 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-2016-8809 exists.\n\nAffected product: Nvidia Gpu Driver. 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-2016-8809/ (Markdown: https://insights.sbomify.com/CVE-2016-8809/index.md)","id":"CVE-2016-8809","markdown":"https://insights.sbomify.com/CVE-2016-8809/index.md","name":"CVE-2016-8809","record":{"aliases":["GHSA-762w-c8mg-xh74"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NVIDIA GPU Driver","requires_auth":"low_privilege","summary":"An attacker can cause denial of service or escalate privileges via improper input buffer validation in the NVIDIA Windows GPU Display Driver kernel mode layer.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"gpu_driver","vendor":"nvidia"}],"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-264","name":null},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"For the NVIDIA Quadro, NVS, and GeForce products, NVIDIA Windows GPU Display Driver R340 before 342.00 and R375 before 375.63 contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgDdiEscape ID 0x70001b2 where the size of an input buffer is not validated, leading to denial of service or potential escalation of privileges.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2016-10-31","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2016-10-31","kind":"exploitdb","ref":"40664","stars":null,"title":"NVIDIA Driver - Incorrect Bounds Check in Escape 0x70001b2"}],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in Quadro, NVS, and GeForce (all versions)","id":"CVE-2016-8809","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nvidia:gpu_driver","products":["nvidia:gpu_driver"],"type":"integer_overflow","year":"2016"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in Quadro, NVS, and GeForce (all versions)","id":"CVE-2016-8810"},"packages":[],"prev":{"headline":"Privilege escalation in Quadro, NVS, and GeForce (all versions)","id":"CVE-2016-8808"},"products":["Quadro, NVS, and GeForce (all versions)"],"published":"2016-11-08","related":[{"cvss_score":10,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2019-5684","kev_date_added":null,"published":"2019-08-06"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2015-5053","kev_date_added":null,"published":"2015-11-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2013-5986","kev_date_added":null,"published":"2014-01-21"},{"cvss_score":9.8,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2019-5685","kev_date_added":null,"published":"2019-08-06"},{"cvss_score":8.8,"headline":"Null dereference in GPU Display Driver","id":"CVE-2018-6247","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":8.8,"headline":"Memory corruption in GPU Display Driver","id":"CVE-2018-6248","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":8.8,"headline":"Null dereference in GPU Display Driver","id":"CVE-2018-6249","kev_date_added":null,"published":"2018-04-02"}],"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-06","vendors":["n/a"]},"summary":"An attacker can cause denial of service or escalate privileges via improper input buffer validation in the NVIDIA Windows GPU Display Driver kernel mode layer.","url":"https://insights.sbomify.com/CVE-2016-8809/"}