Skip to content
Noroxi
NVD / CVE Program· CNA huawei

CVE-2020-9081: There is an improper authorization vulnerability in some Huawei smartphones.

Noroxi assessment

Priority: Monitor (action score 27/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.
  • Severity is disputed: the assigning authority (CNA) scores it 3.5, NVD 6.8.

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 improper authorization vulnerability in some Huawei smartphones. An attacker could perform a series of operation in specific mode to exploit this vulnerability. Successful exploit could allow the attacker to bypass app lock. (Vulnerability ID: HWPSIRT-2019-12144) This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9081.

MediumCVSS 6.8 · v3.1—No exploit No fix recorded
Published
Dec 27, 2024
Updated
Jun 16, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

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%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.8
CNA · huawei
3.5
3.3 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.

Follow CVE-2020-9081

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for huawei records

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.

VendorProduct
huaweimate 20 firmware
huaweimate 20
huaweip30 firmware
huaweip30
huaweip30 pro firmware
huaweip30 pro
huaweiprinceton-al10d firmware
huaweiprinceton-al10d
huaweiyale-al00a firmware
huaweiyale-al00a
huaweiyale-al50a firmware
huaweiyale-al50a

and 2 more

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\(c00e160r3p8\)
  • huawei mate 20 firmwarebefore 10.1.0.160\(c01e160r2p8\)
  • huawei p30 firmwarebefore 10.1.0.160\(c00e160r2p11\)
  • huawei p30 pro firmwarebefore 10.1.0.160\(c01e160r2p8\)
  • huawei p30 pro firmwarebefore 10.1.0.160\(c00e160r2p8\)
  • huawei princeton-al10d firmwarebefore 10.1.0.160\(c00e160r2p11\)
  • huawei yale-al00a firmwarebefore 10.1.0.160\(c00e160r8p12\)
  • huawei yale-al50a firmwarebefore 10.1.0.88\(c00e88r8p1\)
  • huawei yalep-al10b firmwarebefore 10.1.0.160\(c00e160r8p12\)

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(C00E160R3P8), Versions earlier than 10.1.0.160(C01E160R2P8)affected

  • Huawei HUAWEI P30

    • Versions earlier than 10.1.0.160(C00E160R2P11)affected

  • Huawei HUAWEI P30 Pro

    • Versions earlier than 10.1.0.160(C00E160R2P8), Versions earlier than 10.1.0.160(C01E160R2P8)affected

  • Huawei Princeton-AL10D

    • Versions earlier than 10.1.0.160(C00E160R2P11)affected

  • Huawei Yale-AL00A

    • Versions earlier than 10.1.0.160(C00E160R8P12)affected

  • Huawei Yale-AL50A

    • Versions earlier than 10.1.0.88(C00E88R8P1)affected

  • Huawei YaleP-AL10B

    • Versions earlier than 10.1.0.160(C00E160R8P12)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-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

Published before and after this one in the same product

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

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)

CWE-285 · Improper Authorization

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.

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