CVE-2023-52712
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVarious Issues Due To Exposed SMI Handler in AmdPspP2CmboxV2. The first issue can be leveraged to bypass the protections that have been put in place by previous UEFI phases to prevent direct access to the SPI flash. The second issue can be used to both leak and corrupt SMM memory, thus potentially leading code execution in SMM
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in the AMD Platform Security Processor (PSP) P2Cmailbox handler (AmdPspP2CmboxV2) allows an attacker to bypass UEFI phase protections to gain direct access to SPI flash memory, and separately enables SMM memory leakage/corruption leading to potential code execution in System Management Mode.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= ota-curiem-b-bios-2.28CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the system modelCheck if the system is a Huawei Curiem Wfg9b device by inspecting the system information, BIOS identification string, or hardware labelingAffected if The system is a Huawei Curiem Wfg9b
-
Check the installed firmware versionRetrieve the firmware version from the BIOS/UEFI setup or via system firmware information tools (such as dmidecode, biosinfo, or vendor-specific tools). Look for version string 'ota-curiem-b-bios-2.28'Affected if The firmware version equals ota-curiem-b-bios-2.28
-
Confirm the AMD PSP componentVerify the system uses an AMD Platform Security Processor (PSP) by checking CPU information or system documentation. The vulnerability resides in the AmdPspP2CmboxV2 componentAffected if The system contains an AMD PSP and the firmware version matches the affected version
-
Check for recent firmware updatesConsult the vendor (Huawei) support portal or system management interface for any available firmware updates that supersede version 2.28Affected if No firmware update has been applied to address this specific PSP vulnerability
A user is affected if they have a Huawei Curiem Wfg9b system running firmware version ota-curiem-b-bios-2.28 with a vulnerable AMD PSP P2Cmailbox handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply AMD-provided firmware updates and corresponding BIOS updates from motherboard vendors to patch the PSP vulnerability; this cannot be remediated through software code changes.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-52712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data