CVE-2019-5218
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 insufficient authentication vulnerability in Huawei Band 2 and Honor Band 3. The band does not sufficiently authenticate the device try to connect to it in certain scenario. Successful exploit could allow the attacker to spoof then connect to the band.
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 · high confidenceThe Huawei Band 2 and Honor Band 3 fitness trackers contain an insufficient authentication vulnerability in their Bluetooth pairing mechanism. The band fails to properly authenticate devices attempting to connect in certain scenarios, allowing an attacker to spoof a legitimate pairing device and connect to the band without proper verification.
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< eris-b19\/eris-b29_1.2.53< nyx-b10hn_1.5.53CVSS 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.
-
Identify your fitness tracker modelCheck the physical device or its packaging for the model name - look for 'Huawei Band 2' or 'Honor Band 3' or 'Huawei Band 3' labelingAffected if Device is a Huawei Band 2 or Honor Band 3 model
-
Check the firmware version via Huawei Health appOpen the Huawei Health app, select your band, go to Settings or Device Info, and locate the firmware version number displayedAffected if Firmware version cannot be verified or is below the safe versions
-
Verify Huawei Band 2 firmware versionIf you have a Huawei Band 2, confirm the firmware version is eris-b19 or eris-b29_1.2.53 or higherAffected if Firmware version shows a number less than 1.2.53 for eris-b19/eris-b29 builds
-
Verify Honor Band 3 firmware versionIf you have an Honor Band 3, confirm the firmware version is nyx-b10hn_1.5.53 or higherAffected if Firmware version shows a number less than 1.5.53 for nyx-b10hn builds
-
Check Bluetooth pairing behaviorObserve whether the band prompts for confirmation during Bluetooth pairing or automatically accepts connections - the vulnerability allows pairing without proper authentication promptsAffected if Band connects to a device without displaying a typical pairing confirmation or PIN verification
You are affected if you own a Huawei Band 2 or Honor Band 3 with firmware below eris-b19/eris-b29_1.2.53 or nyx-b10hn_1.5.53 respectively, or if the band allows Bluetooth connections without proper authentication prompts.
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.
From vendor dataApply vendor-supplied firmware updates when available. Until then, avoid pairing the band with untrusted devices and disable Bluetooth when not in use in public areas.
- Consultation4.0 h
- Testing8.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 $3,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5218 — 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-2019-5218 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