# CVE-2020-9252: Path traversal in HUAWEI Mate 20

> Attackers can write files to arbitrary paths on Huawei Mate 20 and Honor Magic2 devices due to insufficient pathname validation.

- **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9v6x-99vx-fw68

## What is CVE-2020-9252?

CVE-2020-9252 is a low-severity path traversal vulnerability in HUAWEI Mate 20, published on 17 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HUAWEI Mate 20 versions earlier than 10.1.0.160(C00E160R3P8), HUAWEI Mate 20 X versions earlier than 10.1.0.135(C00E135R2P8), HUAWEI Mate 20 RS versions earlier than 10.1.0.160(C786E160R3P8), and Honor Magic2 smartphones versions earlier than 10.1.0.160(C00E160R2P11) have a path traversal vulnerability. The system does not sufficiently validate certain pathname from certain process, successful exploit could allow the attacker write files to a crafted path.

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

## Which versions are affected by CVE-2020-9252?

It affects 4 products.


Products: Huawei Magic2 Firmware, Huawei Mate 20 Firmware, Huawei Mate 20 Rs Firmware, Huawei Mate 20 X Firmware.

## How do I fix CVE-2020-9252?

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

## Is CVE-2020-9252 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9252 and fix it if it is affected.

What it is: CVE-2020-9252 is a low-severity path traversal vulnerability in HUAWEI Mate 20, published on 17 Jul 2020. 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-2020-9252 in the wild and no public exploit code.

Affected product: HUAWEI Mate 20. 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-2020-9252/ (Markdown: https://insights.sbomify.com/CVE-2020-9252/index.md)
```

## Sources

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

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