Skip to content
Fencer Intel
medium 6.5

CVE-2019-5221 json

There is a path traversal vulnerability on Huawei Share.

published 7y ago modified 4mo ago also EUVD-2019-14826

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

There is a path traversal vulnerability on Huawei Share. The software does not properly validate the path, an attacker could crafted a file path when transporting file through Huawei Share, successful exploit could allow the attacker to transport a file to arbitrary path on the phone. Affected products: Mate 20 X versions earlier than Ever-L29B 9.1.0.300(C432E3R1P12), versions earlier than Ever-L29B 9.1.0.300(C636E3R2P1), and versions earlier than Ever-L29B 9.1.0.300(C185E3R3P1).

Patch / fix

  • huawei mate_20_x_firmware ever-l29b_9.1.0.300\(c185e3r3p1\), ever-l29b_9.1.0.300\(c432e3r1p12\), ever-l29b_9.1.0.300\(c636e3r2p1\)

Is CVE-2019-5221 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Huawei Mate 20 X

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.