dbcve.org
SmarthomeApplication · Huawei

CVE-2017-2704

HIGH · 7.5 CVSS v3.1 Published 2017-11-22
Fix available
A fix is available. Upgrade to after 8.1.2.300 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple Huawei Android applications (SmartHome, HiAPP, HwParentControl, Huawei Pay, and others) store encryption keys directly within the application binary or system storage in an insecure manner. Attackers can perform reverse engineering on the application APK to extract these hardcoded/stored encryption keys, which can then be used to decrypt sensitive data transmitted or stored by the applications.

MitigationReplace hardcoded or insecurely stored encryption keys with proper key management: use hardware-backed secure storage (Android Keystore), implement key derivation from user credentials, or integrate a secure key management service. Re-encrypt any previously protected data using the new key management approach.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SmarthomeApplication
Affected:<= 1.0.2.364
HiappApplication
Affected:<= 7.3.0.303
HwparentcontrolApplication
Affected:<= 2.0.0
HwparentcontrolparentApplication
Affected:<= 5.1.0.12
CrowdtestApplication
Affected:<= 1.5.3
HiwalletApplication
Affected:<= 8.0.0.301
Huawei PayApplication
Affected:<= 8.0.0.300
SkytoneApplication
Affected:<= 8.1.2.300

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. List installed Huawei applications
    Use a package manager or app inventory tool to enumerate all installed applications on the Android device. Look specifically for: SmartHome, HiAPP, HwParentControl, Huawei Pay, Hiwallet, Crowdtest, Skytone, or HwParentControlParent.
    Affected if Any of these eight applications are found installed on the device
  2. Check SmartHome version
    Navigate to Android Settings > Apps > SmartHome > Version, or use 'adb shell dumpsys package com.huawei.smarthome' to retrieve the versionInfo. Compare the version code against 1.0.2.364.
    Affected if Version is 1.0.2.364 or lower
  3. Check Hiapp version
    Navigate to Android Settings > Apps > Hiapp > Version, or use 'adb shell dumpsys package com.huawei.hiapp' to retrieve the versionInfo. Compare against version 7.3.0.303.
    Affected if Version is 7.3.0.303 or lower
  4. Check HwParentControl version
    Navigate to Android Settings > Apps > HwParentControl > Version, or use 'adb shell dumpsys package com.huawei.systemengineer' to retrieve versionInfo. Compare against version 2.0.0.
    Affected if Version is 2.0.0 or lower
  5. Check remaining affected applications
    For Huawei Pay (8.0.0.300), Hiwallet (8.0.0.301), Crowdtest (1.5.3), Skytone (8.1.2.300), and HwParentControlParent (5.1.0.12), use 'adb shell dumpsys package <package_name>' or check via Settings > Apps to retrieve version information and compare against thresholds.
    Affected if Any of these apps are installed at version equal to or below their respective thresholds

If any of the eight affected Huawei applications are installed at a version at or below the specified threshold, the encryption keys may be extractable via APK reverse engineering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 8.1.2.300
Interim mitigation

Replace hardcoded or insecurely stored encryption keys with proper key management: use hardware-backed secure storage (Android Keystore), implement key derivation from user credentials, or integrate a secure key management service. Re-encrypt any previously protected data using the new key management approach.

Fix this in Smarthome Scoped from the published advisory
  • Consultation60.0 h
  • Implementation120.0 h
  • Testing60.0 h
  • Review / QA30.0 h
270.0 hours of engineering $48,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $76,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2704 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data