# CVE-2017-2704: Information disclosure in Smarthome,HiAPP,HwParentControl,HwParentControlParent,Crowdtest,HiWallet,Huawei Pay,Skytone,HwCloudDrive(EMUI6.0),HwPhoneFinder?¡§EMUI6.0??,HwPhoneFinder?¡§EMUI5.1??,HiCinema,HuaweiWear,HiHealthApp,

> Attackers can reverse engineer Huawei mobile applications to extract stored encryption keys, leading to the exposure of sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 16 Sep 2024
- **Also known as:** GHSA-6rf6-j58x-xvx2

## What is CVE-2017-2704?

CVE-2017-2704 is a high-severity vulnerability in Smarthome,HiAPP,HwParentControl,HwParentControlParent,Crowdtest,HiWallet,Huawei Pay,Skytone,HwCloudDrive(EMUI6.0),HwPhoneFinder?¡§EMUI6.0??,HwPhoneFinder?¡§EMUI5.1??,HiCinema,HuaweiWear,HiHealthApp,, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Smarthome 1.0.2.364 and earlier versions,HiAPP 7.3.0.303 and earlier versions,HwParentControl 2.0.0 and earlier versions,HwParentControlParent 5.1.0.12 and earlier versions,Crowdtest 1.5.3 and earlier versions,HiWallet 8.0.0.301 and earlier versions,Huawei Pay 8.0.0.300 and earlier versions,Skytone 8.1.2.300 and earlier versions,HwCloudDrive(EMUI6.0) 8.0.0.307 and earlier versions,HwPhoneFinder(EMUI6.0) 9.3.0.310 and earlier versions,HwPhoneFinder(EMUI5.1) 9.2.2.303 and earlier versions,HiCinema 8.0.2.300 and earlier versions,HuaweiWear 21.0.0.360 and earlier versions,HiHealthApp 3.0.3.300 and earlier versions have an information exposure vulnerability. Encryption keys are stored in the system. The attacker can implement reverse engineering to obtain the encryption keys, causing information exposure.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 14 products.


Products: Huawei Crowdtest, Huawei Hiapp, Huawei Hicinema, Huawei Hihealthapp, Huawei Hiwallet, Huawei Huawei Pay, Huawei Huaweiwear, Huawei Hwclouddrive\(emui6.0\), Huawei Hwparentcontrol, Huawei Hwparentcontrolparent, Huawei Hwphonefinder\(emui5.1\), Huawei Hwphonefinder\(emui6.0\), Huawei Skytone, Huawei Smarthome.

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

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

## Is CVE-2017-2704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2704 is a high-severity vulnerability in Smarthome,HiAPP,HwParentControl,HwParentControlParent,Crowdtest,HiWallet,Huawei Pay,Skytone,HwCloudDrive(EMUI6.0),HwPhoneFinder?¡§EMUI6.0??,HwPhoneFinder?¡§EMUI5.1??,HiCinema,HuaweiWear,HiHealthApp,, 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-2704 in the wild and no public exploit code.

Affected product: Smarthome,HiAPP,HwParentControl,HwParentControlParent,Crowdtest,HiWallet,Huawei Pay,Skytone,HwCloudDrive(EMUI6.0),HwPhoneFinder?¡§EMUI6.0??,HwPhoneFinder?¡§EMUI5.1??,HiCinema,HuaweiWear,HiHealthApp,. 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-2704/ (Markdown: https://insights.sbomify.com/CVE-2017-2704/index.md)
```

## Sources

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

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