Skip to content
Noroxi
CVE-2019-5251· NVD / CVE Program· CNA huawei

There is a path traversal vulnerability in several Huawei smartphones.

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.

MediumCVSS 5.5 · v3.1—No exploit No fix recorded
Published
Dec 13, 2019
Updated
Jun 16, 2026
EPSS
0.8% · 56th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

Affected systems

VendorProduct
huaweihonor v10 firmware
huaweihonor v10
huaweip30 firmware
huaweip30
huaweienjoy 7s firmware
huaweienjoy 7s
huaweimate 20 firmware
huaweimate 20
huaweihonor 9 lite firmware
huaweihonor 9 lite
huaweihonor 9i firmware
huaweihonor 9i

and 6 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • huawei enjoy 7s firmwarebefore 9.1.0.130\(c00e115r2p8t8\)
  • huawei honor 20s firmwarebefore 9.1.1.132\(c00e131r6p1\)
  • huawei honor 9 lite firmwarebefore 9.1.0.143\(c636e5r1p5t8\)
  • huawei honor 9 lite firmwarebefore 9.1.0.130\(c00e112r2p10t8\)
  • huawei honor 9i firmwarebefore 9.1.0.120\(c00e113r1p6t8\)
  • huawei honor v10 firmwarebefore 9.1.0.333\(c00e333r2p1t8\)
  • huawei m6 firmwarebefore 9.1.1.150\(c00e150r1p150\)
  • huawei mate 20 firmwarebefore 9.1.0.139\(c00e133r3p1\)
  • huawei p30 firmwarebefore 9.1.0.226\(c00e220r2p1\)
  • huawei p30 pro firmwarebefore 9.1.0.226\(c00e210r2p1\)

Versions reported by the vendor

Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a Honor V10;P30;Mate 20;Honor 9 Lite;Honor 9i;M6;P30 Pro;Honor 20s

    • Versions earlier than 9.1.0.333(C00E333R2P1T8), Versions earlier than 9.1.0.226(C00E220R2P1), Versions earlier than 9.1.0.130(C00E115R2P8T8), Versions earlier than 9.1.0.139(C00E133R3P1), Versions earlier than 9.1.0.130(C00E112R2P10T8), Versions earlier than 9.1.0.143(C636E5R1P5T8), Versions earlier than 9.1.0.120(C00E113R1P6T8), Versions earlier than 9.1.1.150(C00E150R1P150), Versions earlier than 9.1.0.226(C00E210R2P1), Versions earlier than 9.1.1.132(C00E131R6P1)affected

Other highest-scoring records for the same primary product.

  • CVE-2020-1806Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities.
    28Monitor
  • CVE-2020-1805Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities.
    28Monitor
  • CVE-2020-1804Huawei Honor V10 smartphones with versions earlier than 10.0.0.156(C00E156R2P4) has three out of bounds vulnerabilities.
    28Monitor
  • CVE-2020-1792Honor V10 smartphones with versions earlier than BKL-AL20 10.0.0.156(C00E156R2P4) and versions earlier than BKL-L09 10.0.0.146(C432E4R1P4) h
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records