CVE-2020-9082· NVD / CVE Program· CNA huawei

There is an information disclosure vulnerability in several smartphones.

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.23% (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.

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 an information disclosure vulnerability in several smartphones. The system has a logic judging error under certain scenario, the attacker should gain the permit to execute commands in ADB mode and then do a series of operation on the phone. Successful exploit could allow the attacker to gain certain information from certain apps locked by Applock. (Vulnerability ID: HWPSIRT-2019-07112) This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9082.

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

Info leak

Published: Dec 27, 2024
Updated: Jun 16, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-200

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%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.6
CNA · huawei: 3.5; 1.1 point gap

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

Affected versions

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

huawei mate 20 firmwarebefore 10.1.0.160\(c00\)

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 HUAWEI Mate 20
- Versions earlier than 10.1.0.160(C00)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
← EarlierCVE-2021-22440Jul 13, 2021 · There is a path traversal vulnerability in some Huawei products.
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.

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

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-200 · Exposure of Sensitive Information to an Unauthorized Actor

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

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

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-20200826-16-smartphone-en

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

All records