dbcve.org
P8 Lite FirmwareOperating system · Huawei

CVE-2017-2692

HIGH · 7.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 →
81/100
Remediation priority · High
No privileges

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
The Keyguard application in ALE-L02C635B140 and earlier versions,ALE-L02C636B140 and earlier versions,ALE-L21C10B150 and earlier versions,ALE-L21C185B200 and earlier versions,ALE-L21C432B214 and earlier versions,ALE-L21C464B150 and earlier versions,ALE-L21C636B200 and earlier versions,ALE-L23C605B190 and earlier versions,ALE-TL00C01B250 and earlier versions,ALE-UL00C00B250 and earlier versions,MT7-L09C605B325 and earlier versions,MT7-L09C900B339 and earlier versions,MT7-TL10C900B339 and earlier versions,CRR-CL00C92B172 and earlier versions,CRR-L09C432B180 and earlier versions,CRR-TL00C01B172 and earlier versions,CRR-UL00C00B172 and earlier versions,CRR-UL20C432B171 and earlier versions,GRA-CL00C92B230 and earlier versions,GRA-L09C432B222 and earlier versions,GRA-TL00C01B230SP01 and earlier versions,GRA-UL00C00B230 and earlier versions,GRA-UL00C10B201 and earlier versions,GRA-UL00C432B220 and earlier versions,H60-L04C10B523 and earlier versions,H60-L04C185B523 and earlier versions,H60-L04C636B527 and earlier versions,H60-L04C900B530 and earlier versions,PLK-AL10C00B220 and earlier versions,PLK-AL10C92B220 and earlier versions,PLK-CL00C92B220 and earlier versions,PLK-L01C10B140 and earlier versions,PLK-L01C185B130 and earlier versions,PLK-L01C432B187 and earlier versions,PLK-L01C432B190 and earlier versions,PLK-L01C432B190 and earlier versions,PLK-L01C636B130 and earlier versions,PLK-TL00C01B220 and earlier versions,PLK-TL01HC01B220 and earlier versions,PLK-UL00C17B220 and earlier versions,ATH-AL00C00B210 and earlier versions,ATH-AL00C92B200 and earlier versions,ATH-CL00C92B210 and earlier versions,ATH-TL00C01B210 and earlier versions,ATH-TL00HC01B210 and earlier versions,ATH-UL00C00B210 and earlier versions,RIO-AL00C00B220 and earlier versions,RIO-CL00C92B220 and earlier versions,RIO-TL00C01B220 and earlier versions,RIO-UL00C00B220 and earlier versions have a privilege elevation vulnerability. An attacker may exploit it to launch command injection in order to gain elevated privileges.

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 · moderate confidence

A privilege elevation vulnerability exists in the Keyguard application (lock screen/security module) on multiple Huawei device models. The vulnerability allows an attacker to perform command injection to gain elevated privileges. The Keyguard app runs with elevated system privileges, and successful exploitation enables arbitrary command execution with those elevated rights.

MitigationApply vendor-provided firmware updates for affected device models. Until patches are available, limit physical access to devices and monitor for unauthorized access attempts.

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
P8 Lite FirmwareOperating system
Affected:<= ale-l02c635b140<= ale-l02c636b140<= ale-l21c10b150<= ale-l21c185b200<= ale-l21c432b214<= ale-l21c464b150<= ale-l21c636b200<= ale-l23c605b190<= ale-tl00c01b250<= ale-ul00c00b250.
Mate 7 FirmwareOperating system
Affected:<= mt7-l09c605b325<= mt7-l09c900b339<= mt7-tl10c900b339
Mate S FirmwareOperating system
Affected:<= crr-cl00c92b172<= crr-l09c432b180<= crr-tl00c01b172<= crr-ul00c00b172<= crr-ul20c432b171
P8 FirmwareOperating system
Affected:<= gra-cl00c92b230<= gra-l09c432b222<= gra-tl00c01b230sp01<= gra-ul00c00b230<= gra-ul00c10b201<= gra-ul00c432b220
Honor 6 FirmwareOperating system
Affected:<= h60-l04c10b523<= h60-l04c185b523<= h60-l04c636b527<= h60-l04c900b530
Honor 7 FirmwareOperating system
Affected:<= plk-al10c00b220<= plk-al10c92b220<= plk-cl00c92b220<= plk-l01c10b140<= plk-l01c432b187<= plk-l01c432b190<= plk-l01c636b130<= plk-tl00c01b220<= plk-tl01hc01b220<= plk-ul00c17b220
Shotx FirmwareOperating system
Affected:<= ath-al00c92b200<= ath-cl00c92b210<= ath-tl00c01b210<= ath-tl00hc01b210<= ath-ul00c00b210<= rio-al00c00b220<= ath-al00c00b210
G8 FirmwareOperating system
Affected:<= rio-al00c00b220<= rio-cl00c92b220<= rio-tl00c01b220<= rio-ul00c00b220

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 your Huawei device model
    Go to Settings > About Phone > Model Name (or use 'getprop ro.product.model' via ADB shell)
    Affected if The device model matches one of the affected models: P8 Lite, Mate 7, Mate S, P8, Honor 6, Honor 7, Shotx, or G8
  2. Determine the firmware build version
    Go to Settings > About Phone > Build Number (or use 'getprop ro.build.display.id' via ADB shell)
    Affected if You obtain a build number such as ale-l02c635b140, mt7-l09c605b325, crr-cl00c92b172, gra-ul00c432b220, h60-l04c900b530, plk-al10c92b220, ath-al00c92b200, or rio-al00c220 - but note that these are examples from the affected list
  3. Compare your firmware version against CVE-affected versions
    Cross-reference your exact build number with the version ranges listed in the CVE (for example, if using P8 Lite ale-l02, check if build is <= ale-l02c635b140 or other listed variants)
    Affected if Your exact firmware build number appears in the CVE-affected version list or is lower than the versions listed (the CVE lists specific build numbers with '<=' prefix indicating vulnerable ranges)
  4. Verify the Keyguard application is present
    Check if the Keyguard app exists on the device (typically at /system/app/Keyguard or /system/priv-app/Keyguard) using a file manager or ADB command 'ls -la /system/priv-app/Keyguard'
    Affected if The Keyguard application is installed and runs with elevated system privileges on the device

Your device is affected if it is a Huawei model listed in the CVE and its firmware build number matches or is lower than one of the specific versions enumerated for that model, AND the Keyguard application is present on the device.

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

Apply vendor-provided firmware updates for affected device models. Until patches are available, limit physical access to devices and monitor for unauthorized access attempts.

Fix this in P8 Lite Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2692 — 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-2692 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