{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40262 exists.","fix":"No fix has been published for CVE-2022-40262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-40262 is a high-severity memory corruption vulnerability in AMI Aptio, published on 20 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-40262 and fix it if it is affected.\n\nWhat it is: CVE-2022-40262 is a high-severity memory corruption vulnerability in AMI Aptio, published on 20 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40262 exists.\n\nAffected product: AMI Aptio. 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-40262/ (Markdown: https://insights.sbomify.com/CVE-2022-40262/index.md)","id":"CVE-2022-40262","markdown":"https://insights.sbomify.com/CVE-2022-40262/index.md","name":"CVE-2022-40262","record":{"aliases":["GHSA-5fpf-9vcp-wpjr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation","data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMI Aptio firmware","requires_auth":"high_privilege","summary":"An arbitrary write vulnerability in S3Resume2Pei allows attackers to execute code during boot, bypass security mitigations, and access sensitive memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"aptio_v","vendor":"ami"},{"product":"server_board_m10jnp2sb_firmware","vendor":"intel"}],"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-787","name":"Out-of-bounds Write"},{"id":"CWE-123","name":"Write-what-where Condition"}],"description":"A potential attacker can execute an arbitrary code at the time of the PEI phase and influence the subsequent boot stages. This can lead to the mitigations bypassing, physical memory contents disclosure, discovery of any secrets from any Virtual Machines (VMs) and bypassing memory isolation and confidential computing boundaries. Additionally, an attacker can build a payload which can be injected into the SMRAM memory. This issue affects: Module name: S3Resume2Pei SHA256: 7bb29f05534a8a1e010443213451425098faebd45948a4642db969b19d0253fc Module GUID: 89E549B0-7CFE-449D-9BA3-10D8B2312D71","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"The arbitrary write vulnerability in S3Resume2Pei leads to arbitrary code execution during PEI phase.","id":"CVE-2022-40262","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":"BD Totalys MultiProcessor - Hardcoded Credentials","id":"CVE-2022-40263"},"packages":[],"prev":{"headline":"SMM memory corruption vulnerability in OverClockSmiHandler SMM driver","id":"CVE-2022-40261"},"products":["Aptio"],"published":"2022-09-20","related":[{"cvss_score":8.8,"headline":"Stack overflow vulnerability in SMI handler on SmmSmbiosElog.","id":"CVE-2022-40250","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":8.2,"headline":"Legacy Serial Redirection SMRAM Vulnerabilities","id":"CVE-2025-33045","kev_date_added":null,"published":"2025-09-09"},{"cvss_score":8.2,"headline":"Memory corruption in Aptio","id":"CVE-2022-26873","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":8.2,"headline":"SMM memory corruption vulnerability in OverClockSmiHandler SMM driver","id":"CVE-2022-40261","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":7.8,"headline":"Memory Leak in SmmComuptrace Module","id":"CVE-2024-33656","kev_date_added":null,"published":"2024-08-21"},{"cvss_score":7.8,"headline":"Smm Callout in SmmComputrace Module","id":"CVE-2024-33657","kev_date_added":null,"published":"2024-08-21"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-27","vendors":["AMI"]},"summary":"An arbitrary write vulnerability in S3Resume2Pei allows attackers to execute code during boot, bypass security mitigations, and access sensitive memory.","url":"https://insights.sbomify.com/CVE-2022-40262/"}