# CVE-2017-17161: Auth bypass in Duke-L09

> An attacker can bypass authentication in the Find Phone function to use the phone normally, affecting Huawei smartphone users.

- **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:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j7rm-f9jj-p7c6

## What is CVE-2017-17161?

CVE-2017-17161 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Duke-L09, published on 15 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The 'Find Phone' function in some Huawei smart phones with software earlier than Duke-L09C10B186 versions, earlier than Duke-L09C432B187 versions, earlier than Duke-L09C636B186 versions has an authentication bypass vulnerability. Due to improper authentication realization in the 'Find Phone' function. An attacker may exploit the vulnerability to bypass the 'Find Phone' function in order to use the phone normally.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Duke-L09 Firmware.

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

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

## Is CVE-2017-17161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17161 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. Duke-L09, published on 15 Feb 2018. 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-17161 in the wild and no public exploit code.

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

## Sources

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

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