CVE-2021-37037
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 · uneditedThere is an Invalid address access vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may cause the device to restart.
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 confidenceThis is an invalid memory address access vulnerability in Huawei smartphones that allows an attacker to cause the device to restart. The vulnerability has a CVSS 7.5 indicating it can be exploited over the network without authentication, but the impact is limited to denial of service (device restart) rather than code execution or data exfiltration.
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= 10.1.1= 11.0.0< 2.0= 3.1.1= 4.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Huawei operating systemGo to Settings > About Phone on your Huawei device and identify which OS is listed (Emui, Harmonyos, or Magic Ui)Affected if The device is running Emui, Harmonyos, or Magic Ui
-
Check your Emui version numberIf using Emui, go to Settings > About Phone > Version and note the exact version number displayedAffected if The version is exactly 10.1.1 or exactly 11.0.0
-
Check your Harmonyos version numberIf using Harmonyos, go to Settings > About Phone > Version and note the exact version number displayedAffected if The version is below 2.0 (for example, 1.x versions)
-
Check your Magic Ui version numberIf using Magic Ui, go to Settings > About Phone > Version and note the exact version number displayedAffected if The version is exactly 3.1.1 or exactly 4.0.0
Your device is affected if the OS type matches Emui, Harmonyos, or Magic Ui AND the version exactly matches or falls within the affected ranges listed (10.1.1, 11.0.0 for Emui; below 2.0 for Harmonyos; 3.1.1 or 4.0.0 for Magic Ui).
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.
dbcve · scoped2.0
Apply the vendor-supplied firmware/security update from Huawei. Users should check for system updates in their device settings and ensure they are running the latest vendor-provided patch.
HarmonyOS 2.0 or later (for HarmonyOS devices); Latest available EMUI/Magic UI security update for your specific device model
- Check your device's current EMUI/HarmonyOS/Magic UI version in Settings > About Phone
- For HarmonyOS devices: Upgrade to HarmonyOS 2.0 or later through Settings > System & Updates > Software Update
- For EMUI devices: Apply the latest EMUI security update available for your device model through Settings > System & Updates > Software Update
- For Magic UI devices: Apply the latest Magic UI security update available through Settings > System & Updates > Software Update
- If no update is available, contact your device manufacturer or Huawei support for patch availability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37037 — 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-2021-37037 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