CVE-2017-17161
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 'Find Phone' function in some Huawei smart phones with software earlier than Duke-L09C10B186 versions, earlier than Duke-L09C432B187 versions, earlier than Duke-L09C636B186 versions has an authentication bypass vulnerability. Due to improper authentication realization in the 'Find Phone' function. An attacker may exploit the vulnerability to bypass the 'Find Phone' function in order to use the phone normally.
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 'Find Phone' function in certain Huawei smartphones (Duke-L09 variants) contains an authentication bypass vulnerability due to improper authentication implementation. An attacker can exploit this to bypass the Find Phone function and use the phone normally, effectively circumventing security controls intended to protect a lost or stolen device.
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< duke-l09c10b186< duke-l09c432b187< duke-l09c636b186CVSS 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 modelCheck if the device is a Huawei smartphone, specifically the Duke-L09 or Duke-L09 variant (such as Duke-L09C, Duke-L09C432, Duke-L09C636). This can be done via Settings > About Phone > Model Number, or by checking the device packaging/label.Affected if Device is a Huawei Duke-L09 variant
-
Check installed firmware versionNavigate to Settings > About Phone > Build Number or use *#*#2846579#*#* to access engineering menu to view firmware version. Compare the version string against the three affected version thresholds: duke-l09c10b186, duke-l09c432b187, and duke-l09c636b186.Affected if Firmware version is lower than any of the three thresholds ( duke-l09c10b186, duke-l09c432b187, or duke-l09c636b186 )
-
Verify Find Phone feature statusNavigate to Settings > Find Phone (or Settings > Security > Find Phone) to check if the feature is enabled. The authentication bypass only affects devices where Find Phone has been configured and activated.Affected if Find Phone function is enabled and configured on the device
A user is affected if they own a Huawei Duke-L09 variant running firmware version lower than duke-l09c10b186, duke-l09c432b187, or duke-l09c636b186 AND have the Find Phone feature enabled.
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 dataUpdate affected Huawei smartphones to versions later than Duke-L09C10B186, Duke-L09C432B187, or Duke-L09C636B186 respectively to receive the vendor patch addressing the authentication flaw.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17161 — 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-17161 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