# CVE-2017-8151: Auth bypass in Honor 5S

> An attacker with physical access can bypass authentication to reset passwords and fingerprints on Huawei Honor 5S devices.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pjhp-xj66-5m57

## What is CVE-2017-8151?

CVE-2017-8151 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 5S, 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

Huawei Honor 5S smart phones with software the versions before TAG-TL00C01B173 have an authentication bypass vulnerability due to the improper design of some components. An attacker can get a user's smart phone and install malicious apps in the mobile phone, allowing the attacker to reset the password and fingerprint of the phone without authentication.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Honor 5s Firmware.

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

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

## Is CVE-2017-8151 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Honor 5S

- [CVE-2017-8152](https://insights.sbomify.com/CVE-2017-8152/): Security feature bypass in Honor 5S (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8151 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Honor 5S, 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-8151 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Honor 5S. 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-8151/ (Markdown: https://insights.sbomify.com/CVE-2017-8151/index.md)
```

## Sources

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

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