{"answers":{"affected":"It affects 39 products.","exploited":"There is no known exploitation of CVE-2022-29277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29277 is a high-severity memory corruption vulnerability in n/a, published on 15 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-29277 and fix it if it is affected.\n\nWhat it is: CVE-2022-29277 is a high-severity memory corruption vulnerability in n/a, published on 15 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-29277 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-29277/ (Markdown: https://insights.sbomify.com/CVE-2022-29277/index.md)","id":"CVE-2022-29277","markdown":"https://insights.sbomify.com/CVE-2022-29277/index.md","name":"CVE-2022-29277","record":{"aliases":["GHSA-88wh-qc3q-cp9g"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Insyde BIOS firmware","requires_auth":"low_privilege","summary":"Incorrect pointer checks in the FwBlockServiceSmm driver allow arbitrary RAM modifications, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"genoa_firmware","vendor":"amd"},{"product":"hygon_1_firmware","vendor":"amd"},{"product":"hygon_2_firmware","vendor":"amd"},{"product":"hygon_3_firmware","vendor":"amd"},{"product":"milan_firmware","vendor":"amd"},{"product":"rome_firmware","vendor":"amd"},{"product":"ryzen_5300g_firmware","vendor":"amd"},{"product":"ryzen_5300ge_firmware","vendor":"amd"},{"product":"ryzen_5600g_firmware","vendor":"amd"},{"product":"ryzen_5600ge_firmware","vendor":"amd"},{"product":"ryzen_5600x_firmware","vendor":"amd"},{"product":"ryzen_5700g_firmware","vendor":"amd"},{"product":"ryzen_5700ge_firmware","vendor":"amd"},{"product":"ryzen_5800x3d_firmware","vendor":"amd"},{"product":"ryzen_5800x_firmware","vendor":"amd"},{"product":"ryzen_5900x_firmware","vendor":"amd"},{"product":"ryzen_5950x_firmware","vendor":"amd"},{"product":"snowy_owl_r1000_firmware","vendor":"amd"},{"product":"snowy_owl_r2000_firmware","vendor":"amd"},{"product":"snowy_owl_v2000_firmware","vendor":"amd"},{"product":"snowy_owl_v3000_firmware","vendor":"amd"},{"product":"alder_lake_firmware","vendor":"intel"},{"product":"bakerville_firmware","vendor":"intel"},{"product":"cedar_island_firmware","vendor":"intel"},{"product":"comet_lake-s_firmware","vendor":"intel"},{"product":"denverton_firmware","vendor":"intel"},{"product":"eagle_stream_firmware","vendor":"intel"},{"product":"grangeville_de_ns_firmware","vendor":"intel"},{"product":"granville_de_firmware","vendor":"intel"},{"product":"greenlow-r_firmware","vendor":"intel"},{"product":"greenlow_firmware","vendor":"intel"},{"product":"idaville_firmware","vendor":"intel"},{"product":"mehlow-r_firmware","vendor":"intel"},{"product":"mehlow_firmware","vendor":"intel"},{"product":"purley-r_firmware","vendor":"intel"},{"product":"tatlow_firmware","vendor":"intel"},{"product":"tiger_lake_h\\/up3_firmware","vendor":"intel"},{"product":"whiskey_lake_firmware","vendor":"intel"},{"product":"whitley_firmware","vendor":"intel"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Incorrect pointer checks within the the FwBlockServiceSmm driver can allow arbitrary RAM modifications During review of the FwBlockServiceSmm driver, certain instances of SpiAccessLib could be tricked into writing 0xff to arbitrary system and SMRAM addresses. Fixed in: INTEL Purley-R: 05.21.51.0048 Whitley: 05.42.23.0066 Cedar Island: 05.42.11.0021 Eagle Stream: 05.44.25.0052 Greenlow/Greenlow-R(skylake/kabylake): Trunk Mehlow/Mehlow-R (CoffeeLake-S): Trunk Tatlow (RKL-S): Trunk Denverton: 05.10.12.0042 Snow Ridge: Trunk Graneville DE: 05.05.15.0038 Grangeville DE NS: 05.27.26.0023 Bakerville: 05.21.51.0026 Idaville: 05.44.27.0030 Whiskey Lake: Trunk Comet Lake-S: Trunk Tiger Lake H/UP3: 05.43.12.0052 Alder Lake: 05.44.23.0047 Gemini Lake: Not Affected Apollo Lake: Not Affected Elkhart Lake: 05.44.30.0018 AMD ROME: trunk MILAN: 05.36.10.0017 GENOA: 05.52.25.0006 Snowy Owl: Trunk R1000: 05.32.50.0018 R2000: 05.44.30.0005 V2000: Trunk V3000: 05.44.30.0007 Ryzen 5000: 05.44.30.0004 Embedded ROME: Trunk Embedded MILAN: Trunk Hygon Hygon #1/#2: 05.36.26.0016 Hygon #3: 05.44.26.0007 https://www.insyde.com/security-pledge/SA-2022060","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-29277","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":"Memory corruption in n/a","id":"CVE-2022-29278"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-29276"},"products":["n/a"],"published":"2022-11-15","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":"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":"Incorrect pointer checks in the FwBlockServiceSmm driver allow arbitrary RAM modifications, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2022-29277/"}