Skip to content
Fencer Intel
medium 4.2

CVE-2017-17171 json

Some Huawei smart phones have the denial of service (DoS) vulnerability due to the improper processing of malicious parameters.

published 8y ago modified 4mo ago also EUVD-2017-8337

cvss
4.2
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

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.

Patch / fix

  • huawei mate_8_firmware nxt-al10c00b593, nxt-cl00c92b593, nxt-dl00c17b593, nxt-l09c185b583, nxt-l09c432b582, nxt-l09c605b585custc605d590, nxt-l09c636b598a, nxt-l29c10b583, nxt-l29c185b585, nxt-l29c636b594a, nxtl00c01b593
  • huawei p9_firmware eva-al00c00b398, eva-al10c00b398, eva-cl00c92b398, eva-dl00c17b398, eva-l09c185b391, eva-l09c432b395, eva-l09c464b383, eva-l09c605b392, eva-l19c10b394, eva-l19c432b392, eva-l19c605b390, eva-l19c636b393, eva-l29c636b389, eva-tl00c01b398
  • huawei p9_plus_firmware vie-l09c318b182, vie-l09c432b380, vie-l09c576b180, vie-l29c605b370, vie-l29c636b388

Is CVE-2017-17171 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 4.2 CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 6.3 AV:N/AC:M/Au:S/C:N/I:N/A:C

Affected products

  • Huawei Technologies Co., Ltd. HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.