{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-2558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-2558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2558 is a high-severity memory corruption vulnerability in n/a, published on 12 Apr 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-2558 and fix it if it is affected.\n\nWhat it is: CVE-2016-2558 is a high-severity memory corruption vulnerability in n/a, published on 12 Apr 2016. 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-2016-2558 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-2016-2558/ (Markdown: https://insights.sbomify.com/CVE-2016-2558/index.md)","id":"CVE-2016-2558","markdown":"https://insights.sbomify.com/CVE-2016-2558/index.md","name":"CVE-2016-2558","record":{"aliases":["GHSA-3v54-844g-9c2g"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NVIDIA GPU driver","requires_auth":"none","summary":"Local attackers can exploit memory corruption in the NVIDIA GPU driver to gain privileges, cause crashes, or read sensitive information.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gpu_driver_r340","vendor":"nvidia"},{"product":"gpu_driver_r352","vendor":"nvidia"}],"cvss":{"score":8.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"The Escape interface in the Kernel Mode Driver layer in the NVIDIA GPU graphics driver R340 before 341.95 and R352 before 354.74 on Windows allows local users to obtain sensitive information, cause a denial of service (crash), or gain privileges via unspecified vectors related to an untrusted pointer, which trigger uninitialized or out-of-bounds memory access.","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 n/a","id":"CVE-2016-2558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"phpMyAdmin Cross-site scripting (XSS) vulnerability in SQL parser","id":"CVE-2016-2559"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2016-2557"},"products":["n/a"],"published":"2016-04-12","related":[{"cvss_score":8.4,"headline":"Information disclosure in n/a","id":"CVE-2016-2557","kev_date_added":null,"published":"2016-04-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2016-2556","kev_date_added":null,"published":"2016-04-12"}],"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-05","vendors":["n/a"]},"summary":"Local attackers can exploit memory corruption in the NVIDIA GPU driver to gain privileges, cause crashes, or read sensitive information.","url":"https://insights.sbomify.com/CVE-2016-2558/"}