# CVE-2019-5218: Auth bypass in Huawei Band 2, Honor Band 3

> Attackers can spoof devices to connect to Huawei Band 2 and Honor Band 3 due to insufficient authentication checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xjx5-q997-jj79

## What is CVE-2019-5218?

CVE-2019-5218 is a high-severity authentication bypass vulnerability in Huawei Band 2, Honor Band 3, published on 29 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-5218?

It affects 2 products.


Products: Huawei Band 2 Firmware, Huawei Band 3 Firmware.

## How do I fix CVE-2019-5218?

No fix has been published for CVE-2019-5218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5218 being exploited?

There is no known exploitation of CVE-2019-5218 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5218 and fix it if it is affected.

What it is: CVE-2019-5218 is a high-severity authentication bypass vulnerability in Huawei Band 2, Honor Band 3, published on 29 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5218 in the wild and no public exploit code.

Affected product: Huawei Band 2, Honor Band 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-5218/ (Markdown: https://insights.sbomify.com/CVE-2019-5218/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5218
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5218
- OSV: https://osv.dev/vulnerability/CVE-2019-5218

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-5218/
Summaries are generated and may contain mistakes; the official description above is the record.