dbcve.org
Curiem Wfg9b FirmwareOperating system · Huawei

CVE-2023-52710

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
Huawei Matebook D16(Model: CREM-WXX9, BIOS: v2.26), As the communication buffer size hasn’t been properly validated to be of the expected size, it can partially overlap with the beginning SMRAM.This can be leveraged by a malicious OS attacker to corrupt data structures stored at the beginning of SMRAM and can potentially lead to 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

The vulnerability exists in the System Management Mode (SMM) communication buffer validation of Huawei Matebook D16 BIOS v2.26. The buffer size is not properly validated against the expected size, allowing the communication buffer to partially overlap with the beginning of SMRAM. A malicious OS-level attacker can exploit this to corrupt SMRAM data structures and potentially achieve code execution in SMM, which operates at the highest privilege level on the system.

MitigationApply the vendor-supplied BIOS firmware update from Huawei to patch the SMM communication buffer validation vulnerability. Until the update is available, minimize exposure by ensuring only trusted software runs at the OS level.

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:= ota-curiem-bios-2.29

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 the system model
    Check if the system is a Huawei Matebook D16 or a device using Huawei Curiem Wfg9b firmware. Use system information tools (such as 'dmidecode' on Linux, 'systeminfo' on Windows, or check the BIOS setup screen) to retrieve the system model and manufacturer.
    Affected if The system is a Huawei Matebook D16 or a device with Huawei Curiem Wfg9b firmware.
  2. Retrieve the installed BIOS firmware version
    Access the BIOS/UEFI setup screen during boot (typically by pressing Del, F2, or F12) and navigate to the BIOS version information. Alternatively, use OS-level tools: on Linux, run 'dmidecode -s bios-version'; on Windows, run 'wmic bios get smbiosbiosversion'; or check the 'BIOS Information' section in the System Information tool (msinfo32).
    Affected if The installed BIOS version matches or falls within the affected version range (ota-curiem-bios-2.29 or version 2.26). Compare your retrieved version against the affected versions specified.
  3. Verify SMM is enabled
    Check if System Management Mode is enabled in the BIOS/UEFI settings. Access the BIOS setup during boot and look for SMM-related settings (often under 'Advanced', 'Security', or 'CPU Configuration' sections). On Linux, you can also check 'cat /proc/cpuinfo' for SMME (SMM Enable) flag or use 'dmidecode' to query BIOS settings.
    Affected if SMM is enabled in the BIOS configuration - this is required for the vulnerability to be exploitable.
  4. Inspect SMRAM configuration
    On Linux systems, verify SMRAM configuration by examining /sys/firmware/efi/smm_sw Dispatch_lock and checking if SMRAM regions are properly locked. Use 'efi-checker' or similar tools to parse UEFI variables. Also check dmesg for any SMRAM-related messages indicating whether SMRAM is locked or accessible.
    Affected if SMRAM is not properly locked or is accessible from the OS level, allowing potential buffer overlap with SMRAM regions.

The system is affected if it is a Huawei Matebook D16 or device with Huawei Curiem Wfg9b firmware, has BIOS version 2.26 or 2.29 (ota-curiem-bios-2.29), and has SMM enabled with improperly protected SMRAM.

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 the vendor-supplied BIOS firmware update from Huawei to patch the SMM communication buffer validation vulnerability. Until the update is available, minimize exposure by ensuring only trusted software runs at the OS level.

Fix this in Curiem Wfg9b Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-52710 — 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-52710 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