# CVE-2017-8177: Security feature bypass in HiWallet

> Attackers can bypass signature verification to hijack the HiWallet APK, enabling malicious code execution and potential account takeover.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pxvh-phh5-pgf4

## What is CVE-2017-8177?

CVE-2017-8177 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. HiWallet, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei APP HiWallet earlier than 5.0.3.100 versions do not support signature verification for APK file. An attacker could exploit this vulnerability to hijack the APK and upload modified APK file. Successful exploit could lead to the APP is hijacking.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Huawei Hiwallet.

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

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

## Is CVE-2017-8177 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. HiWallet

- [CVE-2017-17149](https://insights.sbomify.com/CVE-2017-17149/): Auth bypass in Huawei HiWallet App (low 3.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8177 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. HiWallet, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8177 in the wild and no public exploit code.

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

## Sources

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

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