{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35897 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35897 is a medium-severity memory corruption vulnerability in n/a, published on 21 Nov 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-35897 and fix it if it is affected.\n\nWhat it is: CVE-2022-35897 is a medium-severity memory corruption vulnerability in n/a, published on 21 Nov 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-35897 in the wild and no public exploit code.\n\nAffected product: n/a. 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-35897/ (Markdown: https://insights.sbomify.com/CVE-2022-35897/index.md)","id":"CVE-2022-35897","markdown":"https://insights.sbomify.com/CVE-2022-35897/index.md","name":"CVE-2022-35897","record":{"aliases":["GHSA-9g2j-3rfj-c298"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"UEFI firmware","requires_auth":"none","summary":"Stack buffer overflow in InsydeH2O UEFI firmware allows arbitrary code execution if an attacker can modify specific locked variables via SPI access.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kernel","vendor":"insyde"}],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An stack buffer overflow vulnerability leads to arbitrary code execution issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. If the attacker modifies specific UEFI variables, it can cause a stack overflow, leading to arbitrary code execution. The specific variables are normally locked (read-only) at the OS level and therefore an attack would require direct SPI modification. If an attacker can change the values of at least two variables out of three (SecureBootEnforce, SecureBoot, RestoreBootSettings), it is possible to execute arbitrary code.","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-35897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-35898"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-35896"},"products":["n/a"],"published":"2022-11-21","related":[{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-36337","kev_date_added":null,"published":"2022-11-23"},{"cvss_score":8.2,"headline":"Privilege escalation in n/a","id":"CVE-2022-29275","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29276","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29278","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-29279","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30771","kev_date_added":null,"published":"2022-11-15"},{"cvss_score":8.2,"headline":"Memory corruption in n/a","id":"CVE-2022-30772","kev_date_added":null,"published":"2022-11-15"}],"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-04-30","vendors":["n/a"]},"summary":"Stack buffer overflow in InsydeH2O UEFI firmware allows arbitrary code execution if an attacker can modify specific locked variables via SPI access.","url":"https://insights.sbomify.com/CVE-2022-35897/"}