{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21821 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-21821 is a high-severity vulnerability in NVIDIA CUDA Toolkit, published on 29 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-21821 and fix it if it is affected.\n\nWhat it is: CVE-2022-21821 is a high-severity vulnerability in NVIDIA CUDA Toolkit, published on 29 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-21821 in the wild and no public exploit code.\n\nAffected product: NVIDIA CUDA Toolkit. 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-2022-21821/ (Markdown: https://insights.sbomify.com/CVE-2022-21821/index.md)","id":"CVE-2022-21821","markdown":"https://insights.sbomify.com/CVE-2022-21821/index.md","name":"CVE-2022-21821","record":{"aliases":["DEBIAN-CVE-2022-21821","GHSA-gj57-j72r-r89g","UBUNTU-CVE-2022-21821"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CUDA Toolkit SDK","requires_auth":"none","summary":"A remote attacker can achieve code execution and denial of service by tricking a local user into running cuobjdump on a crafted file.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"cuda_toolkit","vendor":"nvidia"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-1285","name":"Improper Validation of Specified Index, Position, or Offset in Input"}],"description":"NVIDIA CUDA Toolkit SDK contains an integer overflow vulnerability in cuobjdump.To exploit this vulnerability, a remote attacker would require a local user to download a specially crafted, corrupted file and locally execute cuobjdump against the file. Such an attack may lead to remote code execution that causes complete denial of service and an impact on data confidentiality and integrity.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer overflow in NVIDIA CUDA Toolkit","id":"CVE-2022-21821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Allocation of Resources Without Limits or Throttling in nvflare","id":"CVE-2022-21822"},"packages":[],"prev":{"headline":"Memory corruption in NVIDIA Data Center GPU Manager","id":"CVE-2022-21820"},"products":["NVIDIA CUDA Toolkit"],"published":"2022-03-29","related":[{"cvss_score":7.8,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2020-5991","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33228","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.3,"headline":"Code injection in CUDA Toolkit","id":"CVE-2025-33229","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.3,"headline":"Command injection in CUDA Toolkit","id":"CVE-2025-33230","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":6.7,"headline":"Other in CUDA Toolkit","id":"CVE-2025-33231","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":5.3,"headline":"Memory corruption in NVIDIA CUDA Toolkit","id":"CVE-2023-25512","kev_date_added":null,"published":"2023-04-22"}],"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-03","vendors":["NVIDIA"]},"summary":"A remote attacker can achieve code execution and denial of service by tricking a local user into running cuobjdump on a crafted file.","url":"https://insights.sbomify.com/CVE-2022-21821/"}