HUAWEI Mate 20 versions Versions earlier than 10.1.0.160(C00E160R3P8);HUAWEI Mate 20 Pro versions Versions earlier than 10.1.0.270(C431E7R1P
HUAWEI Mate 20 versions Versions earlier than 10.1.0.160(C00E160R3P8);HUAWEI Mate 20 Pro versions Versions earlier than 10.1.0.270(C431E7R1P5),Versions earlier than 10.1.0.270(C635E3R1P5),Versions earlier than 10.1.0.273(C636E7R2P4);HUAWEI Mate 20 X versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI P30 versions Versions earlier than 10.1.0.160(C00E160R2P11);HUAWEI P30 Pro versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI Mate 20 RS versions Versions earlier than 10.1.0.160(C786E160R3P8);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);Honor20 versions Versions earlier than 10.0.0.175(C00E58R4P11);Honor20 PRO versions Versions earlier than 10.0.0.194(C00E62R8P12);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);HonorV20 versions Versions earlier than 10.0.0.188(C00E62R2P11) have an improper authentication vulnerability. The system does not properly sign certain encrypted file, the attacker should gain the key used to encrypt the file, successful exploit could cause certain file be forged
- Published
- Aug 11, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
| 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 | mate 20 x firmware | cpe:2.3:o:huawei:mate_20_x_firmware |
| huawei | mate 20 x | cpe:2.3:h:huawei:mate_20_x |
| huawei | p30 firmware | cpe:2.3:o:huawei:p30_firmware |
| huawei | p30 | cpe:2.3:h:huawei:p30 |
| huawei | p30 pro firmware | cpe:2.3:o:huawei:p30_pro_firmware |
| huawei | p30 pro | cpe:2.3:h:huawei:p30_pro |
| huawei | mate 20 rs firmware | cpe:2.3:o:huawei:mate_20_rs_firmware |
| huawei | mate 20 rs | cpe:2.3:h:huawei:mate_20_rs |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei honor 20 firmwarebefore 10.0.0.175\(c00e58r4p11\)
- huawei honor 20 pro firmwarebefore 10.0.0.194\(c00e62r8p12\)
- huawei honor magic 2 firmwarebefore 10.0.0.187\(c00e61r2p11\)
- huawei honor v20 firmwarebefore 10.0.0.188\(c00e62r2p11\)
- huawei mate 20 firmwarebefore 10.1.0.160\(c00e160r3p8\)
- huawei mate 20 pro firmwarebefore 10.1.0.270\(c431e7r1p5\)
- huawei mate 20 pro firmwarebefore 10.1.0.273\(c636e7r2p4\)
- huawei mate 20 pro firmwarebefore 10.1.0.270\(c635e3r1p5\)
- huawei mate 20 rs firmwarebefore 10.1.0.160\(c786e160r3p8\)
- huawei mate 20 x firmwarebefore 10.1.0.160\(c00e160r2p8\)
- huawei p30 firmwarebefore 10.1.0.160\(c00e160r2p11\)
- huawei p30 pro firmwarebefore 10.1.0.160\(c00e160r2p8\)
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;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20
- Versions earlier than 10.1.0.160(C00E160R3P8), Versions earlier than 10.1.0.270(C431E7R1P5),Versions earlier than 10.1.0.270(C635E3R1P5),Versions earlier than 10.1.0.273(C636E7R2P4), Versions earlier than 10.1.0.160(C00E160R2P8), Versions earlier than 10.1.0.160(C00E160R2P11), Versions earlier than 10.1.0.160(C786E160R3P8), Versions earlier than 10.0.0.187(C00E61R2P11), Versions earlier than 10.0.0.175(C00E58R4P11), Versions earlier than 10.0.0.194(C00E62R8P12), Versions earlier than 10.0.0.188(C00E62R2P11)affected
Same product
huawei: all recordsOther 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-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
- CVE-2020-9082There 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.
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
- 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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.