cve.bz

CVE-2019-5251 huawei: Path traversal

5.5 mediumEPSS 0.8%

Medium (5.5) in huawei. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
There is a path traversal vulnerability in several Huawei smartphones. The system does not sufficiently validate certain pathnames from the application. An attacker could trick the user into installing, backing up and restoring a malicious application. Successful exploit could cause information disclosure.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
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-5251 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-5251?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-5251?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-5251 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:honor_v10_firmwarebefore 9.1.0.333\(c00e333r2p1t8\)
huawei:p30_firmwarebefore 9.1.0.226\(c00e220r2p1\)
huawei:enjoy_7s_firmwarebefore 9.1.0.130\(c00e115r2p8t8\)
huawei:mate_20_firmwarebefore 9.1.0.139\(c00e133r3p1\)
huawei:honor_9_lite_firmwarebefore 9.1.0.143\(c636e5r1p5t8\)
huawei:honor_9i_firmwarebefore 9.1.0.120\(c00e113r1p6t8\)
huawei:m6_firmwarebefore 9.1.1.150\(c00e150r1p150\)
huawei:p30_pro_firmwarebefore 9.1.0.226\(c00e210r2p1\)
huawei:honor_20s_firmwarebefore 9.1.1.132\(c00e131r6p1\)
huawei:honor_9_lite_firmwarebefore 9.1.0.130\(c00e112r2p10t8\)

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON