{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-42288 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-42288 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-42288 is a medium-severity vulnerability in NVIDIA DGX servers, published on 13 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-42288 and fix it if it is affected.\n\nWhat it is: CVE-2022-42288 is a medium-severity vulnerability in NVIDIA DGX servers, published on 13 Jan 2023. 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-2022-42288 in the wild and no public exploit code.\n\nAffected product: NVIDIA DGX servers. 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-42288/ (Markdown: https://insights.sbomify.com/CVE-2022-42288/index.md)","id":"CVE-2022-42288","markdown":"https://insights.sbomify.com/CVE-2022-42288/index.md","name":"CVE-2022-42288","record":{"aliases":["GHSA-326f-jv9v-g2jj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA DGX servers","requires_auth":"none","summary":"An unauthorized attacker can guess valid BMC usernames via IPMI oracles, leading to information disclosure on NVIDIA DGX servers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"dgx_a100_firmware","vendor":"nvidia"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"NVIDIA BMC contains a vulnerability in IPMI handler, where an unauthorized attacker can use certain oracles to guess a valid BMC username, which may lead to an information disclosure.","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":"Information disclosure in NVIDIA DGX servers","id":"CVE-2022-42288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in NVIDIA DGX servers","id":"CVE-2022-42289"},"packages":[],"prev":{"headline":"Path traversal in NVIDIA DGX servers","id":"CVE-2022-42287"},"products":["NVIDIA DGX servers"],"published":"2023-01-13","related":[{"cvss_score":9.3,"headline":"CVE","id":"CVE-2023-31029","kev_date_added":null,"published":"2024-01-12"},{"cvss_score":9.3,"headline":"CVE","id":"CVE-2023-31030","kev_date_added":null,"published":"2024-01-12"},{"cvss_score":9,"headline":"CVE","id":"CVE-2023-31024","kev_date_added":null,"published":"2024-01-12"},{"cvss_score":8.4,"headline":"Memory corruption in NVIDIA DGX Servers","id":"CVE-2022-42271","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":8.2,"headline":"Null dereference in NVIDIA DGX A100","id":"CVE-2022-31599","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":8.2,"headline":"Memory corruption in NVIDIA DGX A100","id":"CVE-2022-28200","kev_date_added":null,"published":"2022-07-02"},{"cvss_score":8.1,"headline":"Memory corruption in NVIDIA DGX servers","id":"CVE-2022-42272","kev_date_added":null,"published":"2023-01-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-07","vendors":["NVIDIA"]},"summary":"An unauthorized attacker can guess valid BMC usernames via IPMI oracles, leading to information disclosure on NVIDIA DGX servers.","url":"https://insights.sbomify.com/CVE-2022-42288/"}