dbcve.org
Curiem Wfg9b FirmwareOperating system · Huawei

CVE-2023-52711

HIGH · 7.8 CVSS v3.1 Published 2024-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Various 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 confidence

An exposed SMI (System Management Interrupt) handler in the AmdPspP2CmboxV2 component allows attackers to bypass UEFI phase protections and gain direct access to SPI flash storage. Additionally, the same vulnerability enables leakage and corruption of SMM (System Management Mode) memory, potentially leading to arbitrary code execution at the highest privilege level on x86 systems.

MitigationApply firmware updates provided by AMD and your system OEM vendor to patch the exposed SMI handler. Prioritize systems with sensitive data or those exposed to untrusted peripherals.

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
Curiem Wfg9b FirmwareOperating system
Affected:= curiem-wfg9b_bios_2.28

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify system firmware version
    Retrieve the installed BIOS/firmware version from the system. On Huawei systems, this can be found in the UEFI/BIOS setup utility under 'System Information' or by running 'dmidecode -s bios-version' from Linux. For Windows, use 'wmic bios get smbiosbiosversion'. Compare the version string to '2.28' and confirm the platform is 'curiem-wfg9b'.
    Affected if The installed firmware version is exactly curiem-wfg9b_bios_2.28 (this is the sole affected version per the provided data).
  2. Confirm the system uses AMD PSP hardware
    Verify the system contains an AMD processor with Platform Security Processor (PSP) technology. On Linux, check 'lscpu' or /proc/cpuinfo for 'AuthenticAMD' vendor and PSP-related ACPI tables (look for 'AMD-PSP' or 'AMD-P2C' in dmidecode output).
    Affected if The system is AMD-based with PSP (Platform Security Processor) hardware, required for the AmdPspP2CmboxV2 component to exist.
  3. Check for AmdPspP2CmboxV2 component presence
    Inspect the UEFI/BIOS firmware image for the AmdPspP2CmboxV2 module. This requires extracting and analyzing the firmware binary (using tools like UEFITool or flashrom). Search within the firmware image for the string 'AmdPspP2CmboxV2' or the PSP mailbox driver.
    Affected if The AmdPspP2CmboxV2 component is present in the firmware, indicating the vulnerable code path exists.
  4. Verify SPI flash access exposure
    Examine the SMI handler configuration within the PSP firmware. Look for SMI handlers that expose direct SPI flash read/write capabilities through the P2C (PSP to CPU) mailbox interface. This typically requires firmware binary analysis or reviewing AMD PSP documentation for mailbox command permissions.
    Affected if The SMI handler permits direct SPI flash access without UEFI phase authorization, meaning the P2C mailbox is not properly secured.

You are affected only if your system runs Huawei Curiem Wfg9b firmware version 2.28 with the AmdPspP2CmboxV2 component present and its SMI handler exposing unprotected SPI flash access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates provided by AMD and your system OEM vendor to patch the exposed SMI handler. Prioritize systems with sensitive data or those exposed to untrusted peripherals.

Fix this in Curiem Wfg9b Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52711 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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