CVE-2017-2692

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.

Published: 2017-11-22 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-2692 is rated Moderate Risk (52.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.03%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-2692

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 1.03% +0.83%
2 2025-03-30 0.08% 0.19% +0.11%
3 2025-03-29 — 0.08% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-2692

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-2692

Affected software / configurations for CVE-2017-2692

Vendor Product Version Raw CPE
huawei p8_lite_firmware <= ale-l02c635b140 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l02c636b140 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l21c10b150 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l21c185b200 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l21c432b214 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l21c464b150 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l21c636b200 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-l23c605b190 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-tl00c01b250 cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei p8_lite_firmware <= ale-ul00c00b250. cpe:2.3:o:huawei:p8_lite_firmware:*:*:*:*:*:*:*:*
huawei mate_7_firmware <= mt7-l09c605b325 cpe:2.3:o:huawei:mate_7_firmware:*:*:*:*:*:*:*:*
huawei mate_7_firmware <= mt7-l09c900b339 cpe:2.3:o:huawei:mate_7_firmware:*:*:*:*:*:*:*:*
huawei mate_7_firmware <= mt7-tl10c900b339 cpe:2.3:o:huawei:mate_7_firmware:*:*:*:*:*:*:*:*
huawei mate_s_firmware <= crr-cl00c92b172 cpe:2.3:o:huawei:mate_s_firmware:*:*:*:*:*:*:*:*
huawei mate_s_firmware <= crr-l09c432b180 cpe:2.3:o:huawei:mate_s_firmware:*:*:*:*:*:*:*:*
huawei mate_s_firmware <= crr-tl00c01b172 cpe:2.3:o:huawei:mate_s_firmware:*:*:*:*:*:*:*:*
huawei mate_s_firmware <= crr-ul00c00b172 cpe:2.3:o:huawei:mate_s_firmware:*:*:*:*:*:*:*:*
huawei mate_s_firmware <= crr-ul20c432b171 cpe:2.3:o:huawei:mate_s_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-cl00c92b230 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-l09c432b222 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-tl00c01b230sp01 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-ul00c00b230 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-ul00c10b201 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei p8_firmware <= gra-ul00c432b220 cpe:2.3:o:huawei:p8_firmware:*:*:*:*:*:*:*:*
huawei honor_6_firmware <= h60-l04c10b523 cpe:2.3:o:huawei:honor_6_firmware:*:*:*:*:*:*:*:*
huawei honor_6_firmware <= h60-l04c185b523 cpe:2.3:o:huawei:honor_6_firmware:*:*:*:*:*:*:*:*
huawei honor_6_firmware <= h60-l04c636b527 cpe:2.3:o:huawei:honor_6_firmware:*:*:*:*:*:*:*:*
huawei honor_6_firmware <= h60-l04c900b530 cpe:2.3:o:huawei:honor_6_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-al10c00b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-al10c92b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-cl00c92b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-l01c10b140 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-l01c432b187 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-l01c432b190 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-l01c636b130 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-tl00c01b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-tl01hc01b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei honor_7_firmware <= plk-ul00c17b220 cpe:2.3:o:huawei:honor_7_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-al00c92b200 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-cl00c92b210 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-tl00c01b210 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-tl00hc01b210 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-ul00c00b210 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= rio-al00c00b220 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei shotx_firmware <= ath-al00c00b210 cpe:2.3:o:huawei:shotx_firmware:*:*:*:*:*:*:*:*
huawei g8_firmware <= rio-al00c00b220 cpe:2.3:o:huawei:g8_firmware:*:*:*:*:*:*:*:*
huawei g8_firmware <= rio-cl00c92b220 cpe:2.3:o:huawei:g8_firmware:*:*:*:*:*:*:*:*
huawei g8_firmware <= rio-tl00c01b220 cpe:2.3:o:huawei:g8_firmware:*:*:*:*:*:*:*:*
huawei g8_firmware <= rio-ul00c00b220 cpe:2.3:o:huawei:g8_firmware:*:*:*:*:*:*:*:*

References for CVE-2017-2692

cvelogic Threat Intelligence