CVE-2021-37039
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 Input verification vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may cause Bluetooth DoS.
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 input verification vulnerability in the Bluetooth component of Huawei smartphones. The vulnerability allows an attacker within Bluetooth range to send specially crafted input that is not properly validated, causing the Bluetooth service to become unavailable (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< 2.0= 10.1.1= 11.0.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 the installed operating systemGo to Settings > About Phone on the Huawei smartphone and check whether the OS is listed as HarmonyOS, EMUI, or Magic UI. Note the exact version number displayed.Affected if The device runs HarmonyOS version below 2.0, EMUI version 10.1.1 or 11.0.0, or Magic UI version 3.1.1 or 4.0.0.
-
Confirm the Bluetooth component is activeCheck whether Bluetooth is turned on. On most Huawei devices, swipe down from the top of the screen to access quick settings, or navigate to Settings > Bluetooth, and verify the Bluetooth toggle is enabled.Affected if Bluetooth is currently enabled on the device.
-
Verify the exact OS version numberIn Settings > About Phone, record the full version string (for example, EMUI 10.1.1.150, HarmonyOS 1.0.0, or Magic UI 3.1.1). Compare this to the affected version list: HarmonyOS < 2.0, EMUI = 10.1.1 or 11.0.0, Magic UI = 3.1.1 or 4.0.0.Affected if The installed version matches exactly one of the affected versions listed.
The device is affected if it runs HarmonyOS below version 2.0, EMUI version 10.1.1 or 11.0.0, or Magic UI version 3.1.1 or 4.0.0, and Bluetooth is currently enabled.
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 for affected smartphone models. Until patched, limit Bluetooth exposure to trusted devices and disable Bluetooth when not in use.
HarmonyOS 2.0 or later (verify via system update)
- 1. Identify the current HarmonyOS, EMUI, or Magic UI version on the Huawei device
- 2. For HarmonyOS devices: Upgrade to HarmonyOS 2.0 or later to resolve the Bluetooth input validation vulnerability
- 3. For EMUI devices: Check Huawei's official support pages (consumer.huawei.com) for available security updates addressing CVE-2021-37039
- 4. For Magic UI devices: Check Honor's official support pages for available security updates addressing this vulnerability
- 5. Verify the update has been successfully installed by checking the system software version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37039 — 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-37039 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