CVE-2017-8214

N/A
Published: November 22, 2017 at 07:00 PM UTC
Updated: June 17, 2026 at 01:25 AM UTC
18 products affected across 1 vendorP9 FirmwareP10 Plus FirmwareHonor 9 Firmware

Using Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto by Huawei Technologies Co., Ltd.?

Get instant alerts when new vulnerabilities affect Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

Honor 8,Honor V8,Honor 9,Honor V9,Nova 2,Nova 2 Plus,P9,P10 Plus,Toronto Huawei smart phones with software of versions earlier than FRD-AL00C00B391, versions earlier than FRD-DL00C00B391, versions earlier than KNT-AL10C00B391, versions earlier than KNT-AL20C00B391, versions earlier than KNT-UL10C00B391, versions earlier than KNT-TL10C00B391, versions earlier than Stanford-AL00C00B175, versions earlier than Stanford-AL10C00B175, versions earlier than Stanford-TL00C01B175, versions earlier than Duke-AL20C00B191, versions earlier than Duke-TL30C01B191, versions earlier than Picasso-AL00C00B162, versions earlier than Picasso-TL00C01B162 , versions earlier than Barca-AL00C00B162, versions earlier than Barca-TL00C00B162, versions earlier than EVA-AL10C00B396SP03, versions earlier than EVA-CL00C92B396, versions earlier than EVA-DL00C17B396, versions earlier than EVA-TL00C01B396 , versions earlier than Vicky-AL00AC00B172, versions earlier than Toronto-AL00AC00B191, versions earlier than Toronto-TL10C01B191 have an unlock code verification bypassing vulnerability. An attacker with the root privilege of a mobile can exploit this vulnerability to bypass the unlock code verification and unlock the mobile phone bootloader.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < frd-al00c00b391v < frd-dl00c00b391
Affected range stops below frd-al00c00b391, so it looks safe — our inference, not a vendor statement
Affected range stops below frd-dl00c00b391, so it looks safe — our inference, not a vendor statement
huawei-honor-8 (same device)
v < stanford-al00c00b175v < stanford-al10c00b175v < stanford-tl00c01b175
Affected range stops below stanford-al00c00b175, so it looks safe — our inference, not a vendor statement
Affected range stops below stanford-al10c00b175, so it looks safe — our inference, not a vendor statement
Affected range stops below stanford-tl00c01b175, so it looks safe — our inference, not a vendor statement
huawei-honor-9 (same device)
v < knt-al10c00b391v < knt-al20c00b391v < knt-tl10c00b391v < knt-ul10c00b391
Affected range stops below knt-al10c00b391, so it looks safe — our inference, not a vendor statement
Affected range stops below knt-al20c00b391, so it looks safe — our inference, not a vendor statement
Affected range stops below knt-tl10c00b391, so it looks safe — our inference, not a vendor statement
Affected range stops below knt-ul10c00b391, so it looks safe — our inference, not a vendor statement
huawei-honor-v8 (same device)
v < duke-al20c00b191v < duke-tl30c01b191
Affected range stops below duke-al20c00b191, so it looks safe — our inference, not a vendor statement
Affected range stops below duke-tl30c01b191, so it looks safe — our inference, not a vendor statement
huawei-honor-v9 (same device)
v < picasso-al00c00b162v < picasso-tl00c01b162
Affected range stops below picasso-al00c00b162, so it looks safe — our inference, not a vendor statement
Affected range stops below picasso-tl00c01b162, so it looks safe — our inference, not a vendor statement
huawei-nova-2 (same device)
v < barca-al00c00b162v < barca-tl00c00b162
Affected range stops below barca-al00c00b162, so it looks safe — our inference, not a vendor statement
Affected range stops below barca-tl00c00b162, so it looks safe — our inference, not a vendor statement
huawei-nova-2-plus (same device)
v < vicky-al00ac00b172
Affected range stops below vicky-al00ac00b172, so it looks safe — our inference, not a vendor statement
huawei-p10-plus (same device)
v < eva-al10c00b396sp03v < eva-cl00c92b396v < eva-dl00c17b396v < eva-tl00c01b396
Affected range stops below eva-al10c00b396sp03, so it looks safe — our inference, not a vendor statement
Affected range stops below eva-cl00c92b396, so it looks safe — our inference, not a vendor statement
Affected range stops below eva-dl00c17b396, so it looks safe — our inference, not a vendor statement
Affected range stops below eva-tl00c01b396, so it looks safe — our inference, not a vendor statement
huawei-p9 (same device)
v < toronto-al00ac00b191v < toronto-tl10c01b191
Affected range stops below toronto-al00ac00b191, so it looks safe — our inference, not a vendor statement
Affected range stops below toronto-tl10c01b191, so it looks safe — our inference, not a vendor statement
huawei-toronto (same device)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

CVSS

Confidentiality
COMPLETE
Integrity
COMPLETE
Availability
COMPLETE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-287

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card