CVE-2017-8151

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Huawei Honor 5S smart phones with software the versions before TAG-TL00C01B173 have an authentication bypass vulnerability due to the improper design of some components. An attacker can get a user's smart phone and install malicious apps in the mobile phone, allowing the attacker to reset the password and fingerprint of the phone without authentication.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
24.6%
KEV
Not listed

Published

November 22, 2017

Last Modified

May 13, 2026

Frequently asked(5)

What is CVE-2017-8151?
CVE-2017-8151 is a medium vulnerability published on November 22, 2017. Huawei Honor 5S smart phones with software the versions before TAG-TL00C01B173 have an authentication bypass vulnerability due to the improper design of some components. An attacker can get a user's smart phone and install malicious apps in the mobile phone, allowing the attacker to reset the…
When was CVE-2017-8151 disclosed?
CVE-2017-8151 was first published in the National Vulnerability Database on November 22, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8151 actively exploited?
CVE-2017-8151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-8151?
CVE-2017-8151 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2017-8151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8151

Explore →

Is Your Infrastructure Affected by CVE-2017-8151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.