# CVE-2017-8214: Auth bypass in Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto

> Attackers with root privileges can bypass unlock code verification to unlock the bootloader on various Huawei smartphones.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v494-p7p8-9c4w

## What is CVE-2017-8214?

CVE-2017-8214 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto, published on 22 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto Huawei smart phones with software of versions earlier than FRD-AL00C00B391, versions earlier than FRD-DL00C00B391, versions earlier than KNT-AL10C00B391, versions earlier than KNT-AL20C00B391, versions earlier than KNT-UL10C00B391, versions earlier than KNT-TL10C00B391, versions earlier than Stanford-AL00C00B175, versions earlier than Stanford-AL10C00B175, versions earlier than Stanford-TL00C01B175, versions earlier than Duke-AL20C00B191, versions earlier than Duke-TL30C01B191, versions earlier than Picasso-AL00C00B162, versions earlier than Picasso-TL00C01B162 , versions earlier than Barca-AL00C00B162, versions earlier than Barca-TL00C00B162, versions earlier than EVA-AL10C00B396SP03, versions earlier than EVA-CL00C92B396, versions earlier than EVA-DL00C17B396, versions earlier than EVA-TL00C01B396 , versions earlier than Vicky-AL00AC00B172, versions earlier than Toronto-AL00AC00B191, versions earlier than Toronto-TL10C01B191 have an unlock code verification bypassing vulnerability. An attacker with the root privilege of a mobile can exploit this vulnerability to bypass the unlock code verification and unlock the mobile phone bootloader.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-8214?

It affects 9 products.


Products: Huawei Honor 8 Firmware, Huawei Honor 9 Firmware, Huawei Honor V8 Firmware, Huawei Honor V9 Firmware, Huawei Nova 2 Firmware, Huawei Nova 2 Plus Firmware, Huawei P10 Plus Firmware, Huawei P9 Firmware, Huawei Toronto Firmware.

## How do I fix CVE-2017-8214?

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

## Is CVE-2017-8214 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto

- [CVE-2017-8215](https://insights.sbomify.com/CVE-2017-8215/): Auth bypass in Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto (medium 6.2)
- [CVE-2017-15307](https://insights.sbomify.com/CVE-2017-15307/): Missing authorization in Honor 8 (low 2.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8214 and fix it if it is affected.

What it is: CVE-2017-8214 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto, published on 22 Nov 2017. 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-2017-8214 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto. 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-2017-8214/ (Markdown: https://insights.sbomify.com/CVE-2017-8214/index.md)
```

## Sources

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

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