EmuiOperating system · Huawei

CVE-2023-52372

HIGH · 7.5 CVSS v3.1 Published 2024-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Vulnerability of input parameter verification in the motor module.Successful exploitation of this vulnerability may affect availability.

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 · low confidence

Insufficient technical details available. The CVE describes an input parameter verification vulnerability in a motor module with availability impact, scored at CVSS 7.5. No specific affected products, versions, attack vector, or technical exploitation details are provided in the official description.

MitigationImplement robust input validation and sanitization on all parameters entering the motor module; assume network-adjacent attackers may attempt to send crafted inputs to cause denial of service.

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
EmuiOperating system
Affected:= 12.0.0= 13.0.0
HarmonyosOperating system
Affected:= 2.0.0= 2.1.0= 3.0.0= 3.1.0= 4.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check Huawei EMUI version
    On the Huawei device, go to Settings > About Phone > Version to view the EMUI build number. Alternatively, use 'adb shell getprop ro.build.version.emui' via Android Debug Bridge.
    Affected if The displayed EMUI version is exactly 12.0.0 or 13.0.0
  2. Check HarmonyOS version
    On the Huawei device, go to Settings > About Phone > Version to view the HarmonyOS build number. Alternatively, use 'adb shell getprop ro.build.version.harmonyos' via Android Debug Bridge.
    Affected if The displayed HarmonyOS version is exactly 2.0.0, 2.1.0, 3.0.0, 3.1.0, or 4.0.0
  3. Verify motor module presence
    Since specific technical details about the motor module are not provided, consult your device documentation or contact Huawei support to confirm whether a motor module is present and active on the device.
    Affected if A motor module is present and accessible on the device

A user is affected if their device runs EMUI 12.0.0, EMUI 13.0.0, or any of the specified HarmonyOS versions (2.0.0 through 4.0.0) and contains an accessible motor module.

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

Implement robust input validation and sanitization on all parameters entering the motor module; assume network-adjacent attackers may attempt to send crafted inputs to cause denial of service.

Fix this in Emui Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-52372 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