{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35893 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35893 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35893 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 23 Sep 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-35893 and fix it if it is affected.\n\nWhat it is: CVE-2022-35893 is a high-severity memory corruption vulnerability in Insyde Insydeh2o, published on 23 Sep 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-35893 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-2022-35893/ (Markdown: https://insights.sbomify.com/CVE-2022-35893/index.md)","id":"CVE-2022-35893","markdown":"https://insights.sbomify.com/CVE-2022-35893/index.md","name":"CVE-2022-35893","record":{"aliases":["GHSA-q472-4r55-2p86"],"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":"An SMM memory corruption flaw in InsydeH2O firmware allows attackers to write to SMRAM, potentially escalating privileges to System Management Mode.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"insydeh2o","vendor":"insyde"}],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. An SMM memory corruption vulnerability in the FvbServicesRuntimeDxe driver allows an attacker to write fixed or predictable data to SMRAM. Exploiting this issue could lead to escalating privileges to SMM.","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-2022-35893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"insyde:insydeh2o","products":["insyde:insydeh2o"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-35894"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-35890"},"products":["n/a"],"published":"2022-09-23","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"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-05","vendors":["n/a"]},"summary":"An SMM memory corruption flaw in InsydeH2O firmware allows attackers to write to SMRAM, potentially escalating privileges to System Management Mode.","url":"https://insights.sbomify.com/CVE-2022-35893/"}