# CVE-2019-5221: Path traversal in Mate 20 X

> Attackers can exploit Huawei Share to write files to arbitrary locations on the device due to improper path validation.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-92v3-xfvv-5c39

## What is CVE-2019-5221?

CVE-2019-5221 is a medium-severity path traversal vulnerability in Huawei Mate 20 X, published on 10 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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).

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-5221?

It affects 1 product.


Products: Huawei Mate 20 X Firmware.

## How do I fix CVE-2019-5221?

No fix has been published for CVE-2019-5221 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5221 being exploited?

There is no known exploitation of CVE-2019-5221 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5221 and fix it if it is affected.

What it is: CVE-2019-5221 is a medium-severity path traversal vulnerability in Huawei Mate 20 X, published on 10 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5221 in the wild and no public exploit code.

Affected product: Huawei Mate 20 X. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-5221/ (Markdown: https://insights.sbomify.com/CVE-2019-5221/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5221
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5221
- OSV: https://osv.dev/vulnerability/CVE-2019-5221

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-5221/
Summaries are generated and may contain mistakes; the official description above is the record.