{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2022-32230 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-32230 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-32230 is a high-severity vulnerability in Microsoft Windows 10, published on 14 Jun 2022. 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-32230 and fix it if it is affected.\n\nWhat it is: CVE-2022-32230 is a high-severity vulnerability in Microsoft Windows 10, published on 14 Jun 2022. 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-32230 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows 10. 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-32230/ (Markdown: https://insights.sbomify.com/CVE-2022-32230/index.md)","id":"CVE-2022-32230","markdown":"https://insights.sbomify.com/CVE-2022-32230/index.md","name":"CVE-2022-32230","record":{"aliases":["GHSA-cgqq-pmpm-6gmx"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Windows SMBv3","requires_auth":"none","summary":"An attacker can crash the Windows kernel via a malformed SMBv3 request, causing a Blue Screen of Death and system reboot.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"windows_10","vendor":"microsoft"},{"product":"windows_11","vendor":"microsoft"},{"product":"windows_server_2019","vendor":"microsoft"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"Microsoft Windows SMBv3 suffers from a null pointer dereference in versions of Windows prior to the April, 2022 patch set. By sending a malformed FileNormalizedNameInformation SMBv3 request over a named pipe, an attacker can cause a Blue Screen of Death (BSOD) crash of the Windows kernel. For most systems, this attack requires authentication, except in the special case of Windows Domain Controllers, where unauthenticated users can always open named pipes as long as they can establish an SMB session. Typically, after the BSOD, the victim SMBv3 server will reboot.","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":"SMBv3 FileNormalizedNameInformation NULL Pointer Dereference","id":"CVE-2022-32230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10","products":["microsoft:windows_10","microsoft:windows_11","microsoft:windows_server_2019"],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in Intel(R) Processors","id":"CVE-2022-32231"},"packages":[],"prev":{"headline":"Information disclosure in Rocket.Chat","id":"CVE-2022-32229"},"products":["Windows 10 Version 20H2","Windows 10 Version 21H1","Windows 10 Version 21H2","Windows Server Version 20H2"],"published":"2022-06-14","related":[{"cvss_score":8.8,"headline":"Microsoft Windows Adobe Type Manager Library Remote Code Execution","id":"CVE-2015-2426","kev_date_added":"2022-03-28","published":"2015-07-20"},{"cvss_score":6.6,"headline":"Microsoft Windows Mount Manager Privilege Escalation","id":"CVE-2015-1769","kev_date_added":"2022-05-25","published":"2015-08-15"},{"cvss_score":10,"headline":"Windows Hard Link Elevation of Privilege Vulnerability","id":"CVE-2020-1467","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":9.9,"headline":"Windows TCP/IP Remote Code Execution Vulnerability","id":"CVE-2021-26424","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-28476","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-26867","kev_date_added":null,"published":"2021-03-11"},{"cvss_score":9.9,"headline":"Security feature bypass in Windows","id":"CVE-2019-1384","kev_date_added":null,"published":"2019-11-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-09-16","vendors":["Microsoft"]},"summary":"An attacker can crash the Windows kernel via a malformed SMBv3 request, causing a Blue Screen of Death and system reboot.","url":"https://insights.sbomify.com/CVE-2022-32230/"}