# CVE-2017-17149: Auth bypass in Huawei HiWallet App

> An attacker with root access can bypass Huawei ID verification to arbitrarily change the lock pattern of the HiWallet application.

- **Severity:** Low 3.9 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8fvm-8w45-c4j7

## What is CVE-2017-17149?

CVE-2017-17149 is a low-severity authentication bypass vulnerability in Huawei HiWallet App, published on 9 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei HiWallet App with the versions before 8.0.4 has an arbitrary lock pattern change vulnerability. It needs to verify the user's Huawei ID during lock pattern change. An attacker with root privilege who gets a user's smart phone may bypass Huawei ID verification by special operation. Successful exploit of this vulnerability can allow an attacker to change the lock pattern of HiWallet.

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

It affects 1 product.


Products: Huawei Hiwallet.

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

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

## Is CVE-2017-17149 being exploited?

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

## Other vulnerabilities in Huawei HiWallet App

- [CVE-2017-8177](https://insights.sbomify.com/CVE-2017-8177/): Security feature bypass in HiWallet (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17149 is a low-severity authentication bypass vulnerability in Huawei HiWallet App, published on 9 Mar 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-17149 in the wild and no public exploit code.

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

## Sources

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

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