{"answers":{"affected":"It affects 12 products.","exploited":"There is no known exploitation of CVE-2022-28806 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28806 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28806 is a high-severity memory corruption vulnerability in n/a, published on 4 May 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-28806 and fix it if it is affected.\n\nWhat it is: CVE-2022-28806 is a high-severity memory corruption vulnerability in n/a, published on 4 May 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-28806 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-28806/ (Markdown: https://insights.sbomify.com/CVE-2022-28806/index.md)","id":"CVE-2022-28806","markdown":"https://insights.sbomify.com/CVE-2022-28806/index.md","name":"CVE-2022-28806","record":{"aliases":["GHSA-mj72-h98r-6h24"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fujitsu Laptop BIOS","requires_auth":"low_privilege","summary":"Attackers can corrupt SMRAM via insufficient validation in the FjGabiFlashCoreAbstractionSmm driver, enabling arbitrary code execution in System Management Mode.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lifebook_a3510_firmware","vendor":"fujitsu"},{"product":"lifebook_e449_firmware","vendor":"fujitsu"},{"product":"lifebook_e459_firmware","vendor":"fujitsu"},{"product":"lifebook_e5510_firmware","vendor":"fujitsu"},{"product":"lifebook_u7310_firmware","vendor":"fujitsu"},{"product":"lifebook_u7311_firmware","vendor":"fujitsu"},{"product":"lifebook_u7410_firmware","vendor":"fujitsu"},{"product":"lifebook_u7411_firmware","vendor":"fujitsu"},{"product":"lifebook_u7510_firmware","vendor":"fujitsu"},{"product":"lifebook_u7511_firmware","vendor":"fujitsu"},{"product":"lifebook_u9310_firmware","vendor":"fujitsu"},{"product":"lifebook_u9311_firmware","vendor":"fujitsu"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered on certain Fujitsu LIEFBOOK devices (A3510, U9310, U7511/U7411/U7311, U9311, E5510/E5410, U7510/U7410/U7310, E459/E449) with BIOS versions before v1.09 (A3510), v2.17 (U9310), v2.30 (U7511/U7411/U7311), v2.33 (U9311), v2.23 (E5510), v2.19 (U7510/U7410), v2.13 (U7310), and v1.09 (E459/E449). The FjGabiFlashCoreAbstractionSmm driver registers a Software System Management Interrupt (SWSMI) handler that is not sufficiently validated to ensure that the CommBuffer (or any other communication buffer's nested contents) are not pointing to SMRAM contents. A potential attacker can therefore write fixed data to SMRAM, which could lead to data corruption inside this memory (e.g., change the SMI handler's code or modify SMRAM map structures to break input pointer validation for other SMI handlers). Thus, the attacker could elevate privileges from ring 0 to ring -2 and execute arbitrary code in 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-28806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-28807"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-28805"},"products":["n/a"],"published":"2022-05-04","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-11-04","vendors":["n/a"]},"summary":"Attackers can corrupt SMRAM via insufficient validation in the FjGabiFlashCoreAbstractionSmm driver, enabling arbitrary code execution in System Management Mode.","url":"https://insights.sbomify.com/CVE-2022-28806/"}