cve.bz

CVE-2019-5252 huawei: Improper Authentication

3.5 lowEPSS 0.2%

Low (3.5) in huawei. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.

Severity

CVSS 3.1

3.5 low
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-5252 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-5252?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-5252?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-5252 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:enjoy_8_plus_firmwarebefore 9.1.0.124\(c00e112r1p6t8\)
huawei:y9_firmwarebefore 9.1.0.131\(c432e6r1p5t8\)
huawei:honor_8x_firmwarebefore 9.1.0.217\(c00e15r3p2t8\)
huawei:honor_8x_firmwarebefore 9.1.0.237\(c432e1r3p2t8\)
huawei:honor_8x_firmwarebefore 9.1.0.237\(c636e2r4p1t8\)
huawei:honor_9_lite_firmwarebefore 9.1.0.124\(c00e112r2p10t8\)
huawei:honor_9_lite_firmwarebefore 9.1.0.136\(c636e5r1p5t8\)
huawei:honor_9i_firmwarebefore 9.1.0.115\(c00e113r1p6t8\)
huawei:honor_9i_firmwarebefore 9.1.0.122\(c636e4r1p4t8\)
huawei:y6_pro_firmwarebefore 9.1.0.248\(c636e5r3p1\)

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON