CVE-2017-8154
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Themes App Honor 8 Lite Huawei mobile phones with software of versions before Prague-L31C576B172, versions before Prague-L31C530B160, versions before Prague-L31C432B180 has a man-in-the-middle (MITM) vulnerability due to the use of the insecure HTTP protocol for theme download. An attacker may exploit this vulnerability to tamper with downloaded themes.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Themes App on Huawei Honor 8 Lite devices uses unencrypted HTTP protocol for downloading themes instead of HTTPS. This allows attackers on the same network to perform man-in-the-middle attacks, intercepting and tampering with theme files during download.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< prague-l31c530b160< prague-l31c576b172< prague-l31c432b180CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck if the device is Huawei Honor 8 Lite by going to Settings > About Phone > Model Number or using 'getprop ro.product.model' via ADBAffected if Device model is not Honor 8 Lite (other models are not affected by this specific CVE)
-
Check firmware build number prague-l31c530b160Navigate to Settings > About Phone > Version > Build Number, or use 'getprop ro.build.display.id' via ADB. Compare the build number to prague-l31c530b160Affected if Build number is less than prague-l31c530b160
-
Check firmware build number prague-l31c576b172Navigate to Settings > About Phone > Version > Build Number, or use 'getprop ro.build.display.id' via ADB. Compare the build number to prague-l31c576b172Affected if Build number is less than prague-l31c576b172
-
Check firmware build number prague-l31c432b180Navigate to Settings > About Phone > Version > Build Number, or use 'getprop ro.build.display.id' via ADB. Compare the build number to prague-l31c432b180Affected if Build number is less than prague-l31c432b180
User is affected if the device is a Huawei Honor 8 Lite with firmware build number lower than all three threshold versions (prague-l31c530b160, prague-l31c576b172, or prague-l31c432b180 depending on carrier variant).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement HTTPS with proper certificate validation for all theme downloads, and consider adding integrity verification (e.g., checksums) for downloaded theme packages.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-8154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data