cve.bz

CVE-2017-8215 huawei

6.2 mediumEPSS 0.3%

Medium (6.2) in huawei. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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 a permission control vulnerability. An attacker with the system privilege of a mobile can exploit this vulnerability to bypass the unlock code verification and unlock the mobile phone bootloader.

Severity

CVSS 3.0

6.2 medium
CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-8215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-8215?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-8215?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-8215 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:honor_8_firmwarebefore frd-al00c00b391
huawei:honor_8_firmwarebefore frd-dl00c00b391
huawei:honor_v8_firmwarebefore knt-al10c00b391
huawei:honor_v8_firmwarebefore knt-al20c00b391
huawei:honor_v8_firmwarebefore knt-ul10c00b391
huawei:honor_v8_firmwarebefore knt-tl10c00b391
huawei:honor_9_firmwarebefore stanford-al00c00b175
huawei:honor_9_firmwarebefore stanford-al10c00b175
huawei:honor_9_firmwarebefore stanford-tl00c01b175
huawei:honor_v9_firmwarebefore duke-al20c00b191
huawei:honor_v9_firmwarebefore duke-tl30c01b191
huawei:nova_2_firmwarebefore picasso-al00c00b162
huawei:nova_2_firmwarebefore picasso-tl00c01b162
huawei:nova_2_plus_firmwarebefore barca-al00c00b162
huawei:nova_2_plus_firmwarebefore barca-tl00c00b162
huawei:p9_firmwarebefore eva-al10c00b396sp03
huawei:p9_firmwarebefore eva-cl00c92b396
huawei:p9_firmwarebefore eva-dl00c17b396
huawei:p9_firmwarebefore eva-tl00c01b396
huawei:p10_plus_firmwarebefore vicky-al00ac00b172
huawei:toronto_firmwarebefore toronto-al00ac00b191
huawei:toronto_firmwarebefore toronto-tl10c01b191

References

Check your stackJSON