CVE-2017-2691
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 · uneditedHuawei P9 versions earlier before EVA-AL10C00B373, versions earlier before EVA-CL00C92B373, versions earlier before EVA-DL00C17B373, versions earlier before EVA-TL00C01B373 have a lock-screen bypass vulnerability. An unauthenticated attacker could force the phone to the fastboot mode and delete the user's password file during the reboot process, then login the phone without screen lock password after reboot.
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 Huawei P9 lock-screen bypass vulnerability allows an unauthenticated attacker with physical access to force the device into fastboot mode, delete the stored password file, and then reboot to gain access without authentication. The attack exploits the fastboot mode's ability to modify filesystem data before the lock screen is re-established after reboot.
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< eva-tl00c01b373< eva-dl00c17b373< eva-cl00c92b373< eva-al10c00b373CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelOn the device, go to Settings > About Phone, or run 'adb shell getprop ro.product.model' via ADB to confirm the device is Huawei P9Affected if Device model is not Huawei P9 (different models are not affected by this specific CVE)
-
Check firmware build numberRun 'adb shell getprop ro.build.display.id' or 'adb shell getprop ro.build.version.emui' via ADB, or go to Settings > About Phone > Build number on the deviceAffected if Build number cannot be retrieved or device does not support ADB (unable to determine version status)
-
Compare against affected versionsCompare the retrieved build number against the affected version list: eva-tl00 (versions below c01b373), eva-dl00 (versions below c17b373), eva-cl00 (versions below c92b373), eva-al10 (versions below c00b373)Affected if Installed version matches one of the affected prefixes AND is lower than the corresponding patched version number
User is affected if they have a Huawei P9 device running firmware version lower than eva-tl00c01b373, eva-dl00c17b373, eva-cl00c92b373, or eva-al10c00b373, and the device is physically accessible to an attacker.
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 dataApply the vendor-supplied firmware update (EVA-AL10C00B373, EVA-CL00C92B373, EVA-DL00C17B373, EVA-TL00C01B373 or later) to affected Huawei P9 devices. Organizations should inventory affected devices and deploy updates through their mobile device management infrastructure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2691 — 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-2691 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