Some Huawei smart phones with the versions before Berlin-L21HNC185B381; the versions before Prague-AL00AC00B223; the versions before Prague…

published 2018-05-24 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-8324

cvss: 4.6; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

Some Huawei smart phones with the versions before Berlin-L21HNC185B381; the versions before Prague-AL00AC00B223; the versions before Prague-AL00BC00B223; the versions before Prague-AL00CC00B223; the versions before Prague-L31C432B208; the versions before Prague-TL00AC01B223; the versions before Prague-TL00AC01B223 have an information exposure vulnerability. When the user's smart phone connects to the malicious device for charging, an unauthenticated attacker may activate some specific function by sending some specially crafted messages. Due to insufficient input validation of the messages, successful exploit may cause information exposure.

Patch / fix

fixed in 7

huawei berlin-l21hn_firmware l21hnc185b381
huawei prague-al00a_firmware al00ac00b223
huawei prague-al00b_firmware al00bc00b223
huawei prague-al00c_firmware al00cc00b223
huawei prague-l31_firmware l31c432b208
huawei prague-tl00a_firmware tl00ac01b223
huawei prague-tl10a_firmware tl00ac01b223

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.6	CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Huawei Technologies Co., Ltd. Berlin-L21HN; Prague-AL00A; Prague-AL00B; Prague-AL00C; Prague-L31; Prague-TL00A; Prague-TL10A

Classification

Weakness

CWE-20 Improper Input Validation

References

huawei.com /en/psirt/security-advisories/huawei-sa-20180523-01-phone-en
vendor-advisory

Sources

CVE List CVE-2017-17158
NVD CVE-2017-17158

Fencer Vulns 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.

Summary