dbcve.org
HarmonyosOperating system · Huawei

CVE-2021-37094

HIGH · 7.5 CVSS v3.1 Published 2021-12-07
Fix available
A fix is available. Upgrade to 2.0 or later.
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
There is a Improper Input Validation vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may lead to system denial of service.

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

This is an improper input validation vulnerability (CWE-20) affecting Huawei smartphones. Successful exploitation allows an attacker to send specially crafted input that triggers a denial of service condition, potentially rendering the device unresponsive or requiring reboot.

MitigationApply available Huawei security patches for affected smartphone models. Until patches are available, limit exposure by avoiding untrusted networks and applications that process external input.

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
HarmonyosOperating system
Affected:< 2.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. Confirm Huawei smartphone model
    Check device model in Settings > About Phone. Verify the manufacturer is Huawei and identify the specific model number.
    Affected if Device is not a Huawei smartphone - not affected by this CVE.
  2. Check HarmonyOS version
    Go to Settings > About Phone > HarmonyOS version. Note the exact version number displayed.
    Affected if Version cannot be determined or device runs a different OS - cannot assess for this specific CVE.
  3. Compare against affected version
    Review the HarmonyOS version number. The vulnerability affects all versions prior to 2.0 (for example, 1.x versions are within the affected range).
    Affected if HarmonyOS version is < 2.0 - device is within the affected version range and may be vulnerable.
  4. Verify input processing exposure
    Consider whether the device processes external input from untrusted sources, as exploitation requires sending specially crafted input to trigger the denial of service condition.
    Affected if Device actively processes external input from untrusted networks or applications - exploitation pathway exists.

Device is affected if it is a Huawei smartphone running HarmonyOS version less than 2.0 and processes external input.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0 or later
Fixed in 2.0
Interim mitigation

Apply available Huawei security patches for affected smartphone models. Until patches are available, limit exposure by avoiding untrusted networks and applications that process external input.

Recommended fix Moderate confidence

HarmonyOS 2.0 or later

  1. Check the current HarmonyOS version on the device by navigating to Settings > About Phone > Version
  2. Ensure the device model is compatible with HarmonyOS 2.0 by checking Huawei's official device compatibility list
  3. Connect the device to a stable Wi-Fi network and ensure battery is charged above 50%
  4. Back up important data using Huawei's backup functionality or cloud backup service
  5. Check for system updates by going to Settings > System & Updates > Software Update
  6. If HarmonyOS 2.0 or later is available, download and install the update
  7. After installation, verify the new version by checking Settings > About Phone > Version
Caveat Some legacy applications or custom configurations from earlier HarmonyOS versions may require reconfiguration after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Harmonyos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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