CVE-2017-17171

Some Huawei smart phones have the denial of service (DoS) vulnerability due to the improper processing of malicious parameters. An attacker may trick a target user into installing a malicious APK and launch attacks using a pre-installed app with specific permissions. Successful exploit could allow the app to send specific parameters to the smart phone driver, which will result in system restart.

Published: 2018-06-01 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-17171 is rated Low Risk (30.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.47%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-17171

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.47% +0.43%
2 2025-03-30 0.06% 0.05% -0.01%
3 2025-03-29 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-17171

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.2 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.6 3.6 [email protected]
6.3 2.0 MEDIUM
AV:N/AC:M/Au:S/C:N/I:N/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:C)
Complete availability impact.
 6.8 6.9 [email protected]

Weakness enumeration for CVE-2017-17171

Affected software / configurations for CVE-2017-17171

Vendor Product Version Raw CPE
huawei mate_8_firmware < nxt-al10c00b593 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-cl00c92b593 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-dl00c17b593 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l09c636b598a cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l09c185b583 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l09c432b582 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l09c605b585custc605d590 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l29c10b583 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l29c185b585 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxt-l29c636b594a cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei mate_8_firmware < nxtl00c01b593 cpe:2.3:o:huawei:mate_8_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-al00c00b398 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-al10c00b398 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-cl00c92b398 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-dl00c17b398 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l09c185b391 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l09c432b395 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l09c464b383 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l09c605b392 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware <= eva-l09c636b388 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l19c10b394 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l19c432b392 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l19c605b390 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l19c636b393 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-l29c636b389 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_firmware < eva-tl00c01b398 cpe:2.3:o:huawei:p9_firmware:*:*:*:*:*:*:*:*
huawei p9_plus_firmware < vie-l09c318b182 cpe:2.3:o:huawei:p9_plus_firmware:*:*:*:*:*:*:*:*
huawei p9_plus_firmware < vie-l09c432b380 cpe:2.3:o:huawei:p9_plus_firmware:*:*:*:*:*:*:*:*
huawei p9_plus_firmware < vie-l09c576b180 cpe:2.3:o:huawei:p9_plus_firmware:*:*:*:*:*:*:*:*
huawei p9_plus_firmware < vie-l29c605b370 cpe:2.3:o:huawei:p9_plus_firmware:*:*:*:*:*:*:*:*
huawei p9_plus_firmware < vie-l29c636b388 cpe:2.3:o:huawei:p9_plus_firmware:*:*:*:*:*:*:*:*

References for CVE-2017-17171

cvelogic Threat Intelligence