# CVE-2017-2691: Auth bypass in Huawei P9

> An attacker can bypass the lock screen by forcing fastboot mode to delete the password file, gaining unauthorized access to the device.

- **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-mf6g-r32j-f7qw

## What is CVE-2017-2691?

CVE-2017-2691 is a medium-severity authentication bypass vulnerability in Huawei P9, 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 P9 versions earlier before EVA-AL10C00B373, versions earlier before EVA-CL00C92B373, versions earlier before EVA-DL00C17B373, versions earlier before EVA-TL00C01B373 have a lock-screen bypass vulnerability. An unauthenticated attacker could force the phone to the fastboot mode and delete the user's password file during the reboot process, then login the phone without screen lock password after reboot.

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

It affects 1 product.


Products: Huawei P9 Firmware.

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

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

## Is CVE-2017-2691 being exploited?

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

## Other vulnerabilities in Huawei P9

- [CVE-2017-17319](https://insights.sbomify.com/CVE-2017-17319/): Information disclosure in P9 (medium 5.5)
- [CVE-2017-2713](https://insights.sbomify.com/CVE-2017-2713/): Information disclosure in HUAWEI P9 (medium 5.4)
- [CVE-2017-8148](https://insights.sbomify.com/CVE-2017-8148/): Race condition in P9 (medium 4.7)
- [CVE-2016-8776](https://insights.sbomify.com/CVE-2016-8776/): Auth bypass in P9, P9 Lite EVA-AL10C00,EVA-CL10C00,EVA-DL10C00,EVA-TL10C00,VNS-L21C185, (medium 4.6)
- [CVE-2017-2727](https://insights.sbomify.com/CVE-2017-2727/): Auth bypass in Huawei P9 (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2691 is a medium-severity authentication bypass vulnerability in Huawei P9, 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-2691 in the wild and no public exploit code.

Affected product: Huawei P9. 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-2691/ (Markdown: https://insights.sbomify.com/CVE-2017-2691/index.md)
```

## Sources

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

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