Skip to content
Noroxi
CVE-2020-9252· NVD / CVE Program· CNA huawei

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

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.

LowCVSS 2.3 · v3.1—No exploit No fix recorded
Published
Jul 17, 2020
Updated
Jun 16, 2026
EPSS
0.2% · 12th 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

9

Monitor

Low priority for now.

CVSS
9 / 40 · 2.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

VendorProduct
huaweimate 20 firmware
huaweimate 20
huaweimate 20 x firmware
huaweimate 20 x
huaweimate 20 rs firmware
huaweimate 20 rs
huaweimagic2 firmware
huaweimagic2

Affected versions

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

  • huawei magic2 firmwarebefore 10.1.0.160\(c00e160r2p11\)
  • huawei mate 20 firmwarebefore 10.1.0.160\(c00e160r3p8\)
  • huawei mate 20 rs firmwarebefore 10.1.0.160\(c786e160r3p8\)
  • huawei mate 20 x firmwarebefore 10.1.0.135\(c00e135r2p8\)

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 Magic2

    • Versions earlier than 10.1.0.160(C00E160R2P11)affected

  • n/a HUAWEI Mate 20

    • Versions earlier than 10.1.0.160(C00E160R3P8)affected

  • n/a HUAWEI Mate 20 RS

    • Versions earlier than 10.1.0.160(C786E160R3P8)affected

  • n/a HUAWEI Mate 20 X

    • Versions earlier than 10.1.0.135(C00E135R2P8)affected

Same product

huawei: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-9113HUAWEI Mate 20 versions earlier than 10.0.0.188(C00E74R3P8) have a buffer overflow vulnerability in the Bluetooth module.
    32Monitor
  • CVE-2020-9081There is an improper authorization vulnerability in some Huawei smartphones.
    27Monitor
  • CVE-2020-9244HUAWEI Mate 20 versions Versions earlier than 10.1.0.160(C00E160R3P8);HUAWEI Mate 20 Pro versions Versions earlier than 10.1.0.270(C431E7R1P
    27Monitor
  • CVE-2020-1796There is an improper authorization vulnerability in several smartphones.
    26Monitor
  • CVE-2020-1787HUAWEI Mate 20 smartphones versions earlier than 9.1.0.139(C00E133R3P1) have an improper authentication vulnerability.
    26Monitor
  • CVE-2020-1840HUAWEI Mate 20 smart phones with versions earlier than 10.0.0.175(C00E70R3P8) have an insufficient authentication vulnerability.
    24Monitor

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.

Credits

All researchers

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.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/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.

The bug in code

The whole CWE-22 class

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

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

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