dbcve.org
Mate 20 FirmwareOperating system · Huawei

CVE-2020-1787

MEDIUM · 6.6 CVSS v3.1 Published 2020-01-09
Fix available
A fix is available. Upgrade to 9.1.0.139 or later.
See remediation →
68/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HUAWEI Mate 20 smartphones versions earlier than 9.1.0.139(C00E133R3P1) have an improper authentication vulnerability. The system has a logic error under certain scenario, successful exploit could allow the attacker who gains the privilege of guest user to access to the host user's desktop in an instant, without unlocking the screen lock of the host user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HUAWEI Mate 20 smartphones have an improper authentication vulnerability where a logic error allows a guest user to instantly access the host user's desktop without unlocking the screen lock. This is a privilege escalation flaw in the multi-user account switching mechanism of EMUI.

MitigationApply Huawei firmware update 9.1.0.139(C00E133R1P1) or later which addresses the authentication logic error in multi-user scenarios.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mate 20 FirmwareOperating system
Affected:< 9.1.0.139\(c00e133r3p1\)

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is Huawei Mate 20
    Check device model in Settings > About Phone or run 'adb shell getprop ro.product.model'
    Affected if Device is a Huawei Mate 20 smartphone
  2. Check installed firmware version
    Navigate to Settings > About Phone > Version or run 'adb shell getprop ro.build.version.emui' to view the EMUI firmware version
    Affected if Firmware version is below 9.1.0.139(c00e133r3p1)
  3. Check multi-user feature status
    Navigate to Settings > Users & Accounts > Users to see if multiple user accounts or guest access is configured
    Affected if Multi-user or guest accounts are enabled on the device

The device is affected if it is a Huawei Mate 20 running firmware version below 9.1.0.139(c00e133r3p1) with multi-user or guest accounts enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 9.1.0.139 or later
Fixed in 9.1.0.139
Interim mitigation

Apply Huawei firmware update 9.1.0.139(C00E133R1P1) or later which addresses the authentication logic error in multi-user scenarios.

Fix this in Mate 20 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1787 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data