{"answers":{"affected":"It affects 18 products.","exploited":"There is no known exploitation of CVE-2021-33625 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-33625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-33625 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 3 Feb 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-2021-33625 and fix it if it is affected.\n\nWhat it is: CVE-2021-33625 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 3 Feb 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-2021-33625 in the wild and no public exploit code.\n\nAffected product: Insyde Insydeh2o. 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-2021-33625/ (Markdown: https://insights.sbomify.com/CVE-2021-33625/index.md)","id":"CVE-2021-33625","markdown":"https://insights.sbomify.com/CVE-2021-33625/index.md","name":"CVE-2021-33625","record":{"aliases":["GHSA-mxqq-8hhr-mqww"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"InsydeH2O BIOS","requires_auth":"high_privilege","summary":"Insufficient validation in InsydeH2O BIOS allows attackers to access protected memory regions, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"insydeh2o","vendor":"insyde"},{"product":"fas\\/aff_bios","vendor":"netapp"},{"product":"ruggedcom_ape1808_firmware","vendor":"siemens"},{"product":"simatic_field_pg_m5_firmware","vendor":"siemens"},{"product":"simatic_field_pg_m6_firmware","vendor":"siemens"},{"product":"simatic_ipc127e_firmware","vendor":"siemens"},{"product":"simatic_ipc227g_firmware","vendor":"siemens"},{"product":"simatic_ipc277g_firmware","vendor":"siemens"},{"product":"simatic_ipc327g_firmware","vendor":"siemens"},{"product":"simatic_ipc377g_firmware","vendor":"siemens"},{"product":"simatic_ipc427e_firmware","vendor":"siemens"},{"product":"simatic_ipc477e_firmware","vendor":"siemens"},{"product":"simatic_ipc477e_pro_firmware","vendor":"siemens"},{"product":"simatic_ipc627e_firmware","vendor":"siemens"},{"product":"simatic_ipc647e_firmware","vendor":"siemens"},{"product":"simatic_ipc677e_firmware","vendor":"siemens"},{"product":"simatic_ipc847e_firmware","vendor":"siemens"},{"product":"simatic_itp1000_firmware","vendor":"siemens"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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":"An issue was discovered in Kernel 5.x in Insyde InsydeH2O, affecting HddPassword. Software SMI services that use the Communicate() function of the EFI_SMM_COMMUNICATION_PROTOCOL do not check whether the address of the buffer is valid, which allows use of SMRAM, MMIO, or OS kernel addresses.","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-2021-33625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"insyde:insydeh2o","products":["insyde:insydeh2o"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-33626"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-33624"},"products":["n/a"],"published":"2022-02-03","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-41842","kev_date_added":null,"published":"2022-01-05"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22612","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22613","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-22614","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2023-22615","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-36448","kev_date_added":null,"published":"2022-09-28"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-35893","kev_date_added":null,"published":"2022-09-23"}],"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":"2026-08-11","vendors":["n/a"]},"summary":"Insufficient validation in InsydeH2O BIOS allows attackers to access protected memory regions, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2021-33625/"}