CVE-2021-40002
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 · uneditedThe Bluetooth module has an out-of-bounds write vulnerability. Successful exploitation of this vulnerability may result in malicious command execution at the remote end.
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 out-of-bounds write vulnerability in a Bluetooth module that allows an attacker to write data beyond allocated memory boundaries. Successful exploitation can lead to remote command execution, likely by corrupting function pointers or overwriting critical memory structures on the targeted device.
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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Huawei HarmonyOS is in useIdentify the operating system running on the device. On HarmonyOS devices, check system settings or use 'getprop ro.build.version.emui' or similar system information commands to verify HarmonyOS is the active OS.Affected if The device is not running Huawei HarmonyOS, then this specific CVE does not apply.
-
Determine HarmonyOS versionCheck the installed HarmonyOS version. On most devices, go to Settings > About Phone > Version, or use command-line tools like 'getprop ro.build.version.sdk' or 'settings get system version' to retrieve the version number.Affected if The installed HarmonyOS version is any version prior to 2.0 (e.g., 1.x, 1.5, 1.0), indicating the device falls within the affected range.
-
Verify Bluetooth module is enabledCheck if Bluetooth is currently active on the device. This can be done via system settings (Settings > Bluetooth) or by using Bluetooth status commands such as 'settings get global bluetooth_on' or checking the Bluetooth service status.Affected if Bluetooth is enabled and actively used, as the vulnerability exists within the Bluetooth module and requires Bluetooth communication to be possible.
-
Assess Bluetooth exposureDetermine the device's Bluetooth accessibility. Check if Bluetooth is set to discoverable or connectable modes, and evaluate whether the device is used in environments with untrusted Bluetooth devices nearby.Affected if Bluetooth is enabled and the device can accept connections from other Bluetooth devices, creating the attack surface for exploitation.
A device is affected if it runs Huawei HarmonyOS with a version number below 2.0 and has Bluetooth functionality enabled, as the out-of-bounds write vulnerability resides in the Bluetooth module and could allow remote command execution.
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 vendor-supplied patches or firmware updates for the affected Bluetooth module. If no patch is available, consider network-level mitigations to limit Bluetooth exposure and monitor for anomalous Bluetooth activity.
HarmonyOS 2.0
- Upgrade the device to HarmonyOS 2.0 or later to resolve the out-of-bounds write vulnerability in the Bluetooth module
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40002 — 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-40002 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