ALE-L02C635B140 and earlier versions,ALE-L02C636B140 and earlier versions,ALE-L21C10B150 and earlier versions,ALE-L21C185B200 and earlier ve
ALE-L02C635B140 and earlier versions,ALE-L02C636B140 and earlier versions,ALE-L21C10B150 and earlier versions,ALE-L21C185B200 and earlier versions,ALE-L21C432B214 and earlier versions,ALE-L21C464B150 and earlier versions,ALE-L21C636B200 and earlier versions,ALE-L23C605B190 and earlier versions,ALE-TL00C01B250 and earlier versions,ALE-UL00C00B250 and earlier versions,MT7-L09C605B325 and earlier versions,MT7-L09C900B339 and earlier versions,MT7-TL10C900B339 and earlier versions,CRR-CL00C92B172 and earlier versions,CRR-L09C432B180 and earlier versions,CRR-TL00C01B172 and earlier versions,CRR-UL00C00B172 and earlier versions,CRR-UL20C432B171 and earlier versions,GRA-CL00C92B230 and earlier versions,GRA-L09C432B222 and earlier versions,GRA-TL00C01B230SP01 and earlier versions,GRA-UL00C00B230 and earlier versions,GRA-UL00C10B201 and earlier versions,GRA-UL00C432B220 and earlier versions,H60-L04C10B523 and earlier versions,H60-L04C185B523 and earlier versions,H60-L04C636B527 and earlier versions,H60-L04C900B530 and earlier versions,PLK-AL10C00B220 and earlier versions,PLK-AL10C92B220 and earlier versions,PLK-CL00C92B220 and earlier versions,PLK-L01C10B140 and earlier versions,PLK-L01C185B130 and earlier versions,PLK-L01C432B187 and earlier versions,PLK-L01C432B190 and earlier versions,PLK-L01C432B190 and earlier versions,PLK-L01C636B130 and earlier versions,PLK-TL00C01B220 and earlier versions,PLK-TL01HC01B220 and earlier versions,PLK-UL00C17B220 and earlier versions,ATH-AL00C00B210 and earlier versions,ATH-AL00C92B200 and earlier versions,ATH-CL00C92B210 and earlier versions,ATH-TL00C01B210 and earlier versions,ATH-TL00HC01B210 and earlier versions,ATH-UL00C00B210 and earlier versions,RIO-AL00C00B220 and earlier versions,RIO-CL00C92B220 and earlier versions,RIO-TL00C01B220 and earlier versions,RIO-UL00C00B220 and earlier versions have a path traversal vulnerability. An attacker may exploit it to decompress malicious files into a target path.
- Published
- Nov 22, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 63th percentile
- CWE
- CWE-22
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| huawei | p8 lite firmware | cpe:2.3:o:huawei:p8_lite_firmware |
| huawei | p8 lite | cpe:2.3:h:huawei:p8_lite |
| huawei | mate 7 firmware | cpe:2.3:o:huawei:mate_7_firmware |
| huawei | mate 7 | cpe:2.3:h:huawei:mate_7 |
| huawei | mate s firmware | cpe:2.3:o:huawei:mate_s_firmware |
| huawei | mate s | cpe:2.3:h:huawei:mate_s |
| huawei | p8 firmware | cpe:2.3:o:huawei:p8_firmware |
| huawei | p8 | cpe:2.3:h:huawei:p8 |
| huawei | honor 6 firmware | cpe:2.3:o:huawei:honor_6_firmware |
| huawei | honor 6 | cpe:2.3:h:huawei:honor_6 |
| huawei | honor 7 firmware | cpe:2.3:o:huawei:honor_7_firmware |
| huawei | honor 7 | cpe:2.3:h:huawei:honor_7 |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei g8 firmwareup to rio-al00c00b220 inclusive
- huawei g8 firmwareup to rio-ul00c00b220 inclusive
- huawei g8 firmwareup to rio-tl00c01b220 inclusive
- huawei g8 firmwareup to rio-cl00c92b220 inclusive
- huawei honor 6 firmwareup to h60-l04c185b523 inclusive
- huawei honor 6 firmwareup to h60-l04c900b530 inclusive
- huawei honor 6 firmwareup to h60-l04c636b527 inclusive
- huawei honor 6 firmwareup to h60-l04c10b523 inclusive
- huawei honor 7 firmwareup to plk-tl01hc01b220 inclusive
- huawei honor 7 firmwareup to plk-al10c00b220 inclusive
- huawei honor 7 firmwareup to plk-al10c92b220 inclusive
- huawei honor 7 firmwareup to plk-cl00c92b220 inclusive
- huawei honor 7 firmwareup to plk-l01c10b140 inclusive
- huawei honor 7 firmwareup to plk-l01c432b187 inclusive
- huawei honor 7 firmwareup to plk-l01c432b190 inclusive
- huawei honor 7 firmwareup to plk-l01c636b130 inclusive
- huawei honor 7 firmwareup to plk-tl00c01b220 inclusive
- huawei honor 7 firmwareup to plk-ul00c17b220 inclusive
- huawei mate 7 firmwareup to mt7-l09c605b325 inclusive
- huawei mate 7 firmwareup to mt7-tl10c900b339 inclusive
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.
Huawei Technologies Co., Ltd. P8 Lite,Mate 7,Mate S,P8,honor 6,honor 7,SHOTX,G8,
- ALE-L02C635B140 and earlier versions,ALE-L02C636B140 and earlier versions,ALE-L21C10B150 and earlier versions,ALE-L21C185B200 and earlier versions,ALE-L21C432B214 and earlier versions,ALE-L21C464B150 affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-2692The Keyguard application in ALE-L02C635B140 and earlier versions,ALE-L02C636B140 and earlier versions,ALE-L21C10B150 and earlier versions,AL31Monitor
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.
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 researchersFinders, 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.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
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.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
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 helpChange 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-20170125-01-emui-en
- www.securityfocus.com/bid/95919
Vendor advisories and official records. Exploit/PoC links are deliberately left out.