{"answers":{"affected":"It affects 10 products.","exploited":"There is no known exploitation of CVE-2022-34301 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-34301 is a medium-severity vulnerability in Microsoft Windows 10, published on 26 Aug 2022. 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-2022-34301 and fix it if it is affected.\n\nWhat it is: CVE-2022-34301 is a medium-severity vulnerability in Microsoft Windows 10, published on 26 Aug 2022. 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-2022-34301 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-34301/ (Markdown: https://insights.sbomify.com/CVE-2022-34301/index.md)","id":"CVE-2022-34301","markdown":"https://insights.sbomify.com/CVE-2022-34301/index.md","name":"CVE-2022-34301","record":{"aliases":["GHSA-7j33-663j-fx7f"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Secure Boot bootloader","requires_auth":"high_privilege","summary":"Attackers can bypass Secure Boot protections by replacing the signed bootloader, enabling arbitrary code execution during the pre-boot stage.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cryptopro_securedisk_for_bitlocker","vendor":"kidan"},{"product":"windows_10","vendor":"microsoft"},{"product":"windows_11","vendor":"microsoft"},{"product":"windows_8.1","vendor":"microsoft"},{"product":"windows_rt_8.1","vendor":"microsoft"},{"product":"windows_server_2012","vendor":"microsoft"},{"product":"windows_server_2016","vendor":"microsoft"},{"product":"windows_server_2019","vendor":"microsoft"},{"product":"windows_server_2022","vendor":"microsoft"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A flaw was found in CryptoPro Secure Disk bootloaders before 2022-06-01. An attacker may use this bootloader to bypass or tamper with Secure Boot protections. In order to load and execute arbitrary code in the pre-boot stage, an attacker simply needs to replace the existing signed bootloader currently in use with this bootloader. Access to the EFI System Partition is required for booting using external media.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-07","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-07T08:50:29Z","kind":"github_poc","ref":"https://github.com/TheMalwareGuardian/CVE-2022-34301","stars":1,"title":"CVE-2022-34301 - Secure Boot bypass via Eurosoft signed UEFI Shell (esdiags.efi) - BYOVUA technique exploiting mm command for gSecurity2 corruption to load unsigned UEFI applications."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2022-34301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10","products":["microsoft:windows_10","microsoft:windows_11","microsoft:windows_8.1","microsoft:windows_rt_8.1","microsoft:windows_server_2012","microsoft:windows_server_2016","microsoft:windows_server_2019","microsoft:windows_server_2022","redhat:enterprise_linux"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2022-34302"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-34300"},"products":["n/a"],"published":"2022-08-26","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can bypass Secure Boot protections by replacing the signed bootloader, enabling arbitrary code execution during the pre-boot stage.","url":"https://insights.sbomify.com/CVE-2022-34301/"}