dbcve.org
Honor 7 Lite FirmwareOperating system · Huawei

CVE-2017-8206

MEDIUM · 6.8 CVSS v3.0 Published 2017-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
HONOR 7 Lite mobile phones with software of versions earlier than NEM-L21C432B352 have an App Lock bypass vulnerability. An attacker could perform specific operations to bypass the App Lock to use apps on a target mobile phone temporarily.

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 confidence

HONOR 7 Lite mobile phones with software versions earlier than NEM-L21C432B352 contain an App Lock bypass vulnerability. An attacker with physical access can perform specific operations to temporarily bypass the App Lock authentication mechanism and access locked applications without proper credentials.

MitigationUpdate HONOR 7 Lite software to version NEM-L21C432B352 or later to patch the App Lock bypass vulnerability.

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
Honor 7 Lite FirmwareOperating system
Affected:< nem-l21c432b352

CVSS 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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Go to Settings > About Phone on the device and verify the model name is HONOR 7 Lite or the equivalent model number (NEM-L21)
    Affected if Device is not a HONOR 7 Lite (NEM-L21)
  2. Check installed firmware version
    Go to Settings > About Phone > Version and record the build number or firmware version listed
    Affected if Cannot determine firmware version from device settings
  3. Compare firmware version against affected range
    Compare the installed build number to NEM-L21C432B352 - note that versions earlier than this (e.g., C432B340, C432B342, etc.) are affected
    Affected if Installed firmware version is less than NEM-L21C432B352 (e.g., NEM-L21C432B340, NEM-L21C432B342, etc.)
  4. Verify App Lock configuration
    Check if App Lock is configured on the device by going to Settings > Security > App Lock (or Settings > Privacy > App Lock on some builds)
    Affected if App Lock is configured on an affected firmware version

The device is affected if it is a HONOR 7 Lite (NEM-L21) running firmware version earlier than NEM-L21C432B352 and has App Lock enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update HONOR 7 Lite software to version NEM-L21C432B352 or later to patch the App Lock bypass vulnerability.

Fix this in Honor 7 Lite Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8206 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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