NVD / CVE Program· CNA huawei

CVE-2021-22440: There is a path traversal vulnerability in some Huawei products.

Noroxi assessment

Priority: Monitor (action score 18/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

There is a path traversal vulnerability in some Huawei products. The vulnerability is due to that the software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly validate the pathname. Successful exploit could allow the attacker to access a location that is outside of the restricted directory by a crafted filename. Affected product versions include:HUAWEI Mate 20 9.0.0.195(C01E195R2P1), 9.1.0.139(C00E133R3P1);HUAWEI Mate 20 Pro 9.0.0.187(C432E10R1P16), 9.0.0.188(C185E10R2P1), 9.0.0.245(C10E10R2P1), 9.0.0.266(C432E10R1P16), 9.0.0.267(C636E10R2P1), 9.0.0.268(C635E12R1P16), 9.0.0.278(C185E10R2P1); Hima-L29C 9.0.0.105(C10E9R1P16), 9.0.0.105(C185E9R1P16), 9.0.0.105(C636E9R1P16); Laya-AL00EP 9.1.0.139(C786E133R3P1); OxfordS-AN00A 10.1.0.223(C00E210R5P1); Tony-AL00B 9.1.0.257(C00E222R2P1).

MediumCVSS 4.6 · v3.1—No exploit No fix recorded

Path traversal

Published: Jul 13, 2021
Updated: Jun 16, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 18 / 40 · 4.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
huawei	mate 20 firmware	cpe:2.3:o:huawei:mate_20_firmware
huawei	mate 20	cpe:2.3:h:huawei:mate_20
huawei	mate 20 pro firmware	cpe:2.3:o:huawei:mate_20_pro_firmware
huawei	mate 20 pro	cpe:2.3:h:huawei:mate_20_pro
huawei	hima-l29c firmware	cpe:2.3:o:huawei:hima-l29c_firmware
huawei	hima-l29c	cpe:2.3:h:huawei:hima-l29c
huawei	laya-al00ep firmware	cpe:2.3:o:huawei:laya-al00ep_firmware
huawei	laya-al00ep	cpe:2.3:h:huawei:laya-al00ep
huawei	oxfords-an00a firmware	cpe:2.3:o:huawei:oxfords-an00a_firmware
huawei	oxfords-an00a	cpe:2.3:h:huawei:oxfords-an00a
huawei	tony-al00b firmware	cpe:2.3:o:huawei:tony-al00b_firmware
huawei	tony-al00b	cpe:2.3:h:huawei:tony-al00b

Affected versions

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

huawei hima-l29c firmware9.0.0.105(c10e9r1p16)
huawei hima-l29c firmware9.0.0.105(c185e9r1p16)
huawei hima-l29c firmware9.0.0.105(c636e9r1p16)
huawei laya-al00ep firmware9.1.0.139(c786e133r3p1)
huawei mate 20 firmware9.0.0.195(c01e195r2p1)
huawei mate 20 firmware9.1.0.139(c00e133r3p1)
huawei mate 20 pro firmware9.0.0.187(c432e10r1p16)
huawei mate 20 pro firmware9.0.0.188(c185e10r2p1)
huawei mate 20 pro firmware9.0.0.245(c10e10r2p1)
huawei mate 20 pro firmware9.0.0.266(c432e10r1p16)
huawei mate 20 pro firmware9.0.0.267(c636e10r2p1)
huawei mate 20 pro firmware9.0.0.268(c635e12r1p16)
huawei mate 20 pro firmware9.0.0.278(c185e10r2p1)
huawei oxfords-an00a firmware10.1.0.223(c00e210r5p1)
huawei tony-al00b firmware9.1.0.257(c00e222r2p1)

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 HUAWEI Mate 20;HUAWEI Mate 20 Pro;Hima-L29C;Laya-AL00EP;OxfordS-AN00A;Tony-AL00B
- 9.0.0.195(C01E195R2P1),9.1.0.139(C00E133R3P1), 9.0.0.187(C432E10R1P16),9.0.0.188(C185E10R2P1),9.0.0.245(C10E10R2P1),9.0.0.266(C432E10R1P16),9.0.0.267(C636E10R2P1),9.0.0.268(C635E12R1P16),9.0.0.278(C185E10R2P1), 9.0.0.105(C10E9R1P16),9.0.0.105(C185E9R1P16),9.0.0.105(C636E9R1P16), 9.1.0.139(C786E133R3P1), 10.1.0.223(C00E210R5P1), 9.1.0.257(C00E222R2P1)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

Published before and after this one in the same product

← EarlierCVE-2020-9109Oct 12, 2020 · There is an information disclosure vulnerability in several smartphones.
18Monitor
← EarlierCVE-2020-9092Oct 19, 2020 · HUAWEI Mate 20 versions earlier than 10.1.0.163(C00E160R3P8) have a JavaScript injection vulnerability.
18Monitor
Later →CVE-2020-9082Dec 27, 2024 · There is an information disclosure vulnerability in several smartphones.
18Monitor

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.

No history yet (it accumulates with the daily EPSS job).

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-21-0546 · Jul 5, 2021(Huawei Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Physical access to the device is required.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Physical
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
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:P/AC:L/PR:N/UI:N/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.

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

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

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.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.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

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

References

www.huawei.com/en/psirt/security-advisories/huawei-sa-20210630-01-pathtraversal-en

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

All records