dbcve.org
Mate 30 Pro FirmwareOperating system · Huawei

CVE-2020-1838

MEDIUM · 5.5 CVSS v3.1 Published 2020-07-06
Fix available
A fix is available. Upgrade to 10.1.0.150 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 30 Pro with versions earlier than 10.1.0.150(C00E136R5P3) have is an improper authentication vulnerability. The device does not sufficiently validate certain credential of user's face, an attacker could craft the credential of the user, successful exploit could allow the attacker to pass the authentication with the crafted credential.

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

This is an improper authentication vulnerability in the face recognition system of HUAWEI Mate 30 Pro. The device fails to sufficiently validate biometric credentials during face authentication, allowing an attacker to craft a fake biometric credential that successfully bypasses the authentication mechanism.

MitigationUpdate HUAWEI Mate 30 Pro to version 10.1.0.150(C00E136R5P3) or later to patch the face authentication validation flaw. Until updated, consider using alternative authentication methods (PIN, fingerprint) for sensitive operations.

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 30 Pro FirmwareOperating system
Affected:< 10.1.0.150\(c00e136r5p3\)

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 30 Pro
    Check the device model in Settings > About Phone to verify it is a HUAWEI Mate 30 Pro
    Affected if Device is not a HUAWEI Mate 30 Pro
  2. Identify installed firmware version
    Navigate to Settings > About Phone > Version and record the build number or firmware version
    Affected if Firmware version is earlier than 10.1.0.150(c00e136r5p3)
  3. Verify face recognition is configured
    Check Settings > Face ID & Password or Settings > Security > Face Recognition to see if face recognition has been set up as an authentication method
    Affected if Face recognition is enabled and used for device unlock or authentication

Device is affected if it is a HUAWEI Mate 30 Pro running firmware version below 10.1.0.150(c00e136r5p3) with face recognition enabled as an authentication mechanism

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 10.1.0.150 or later
Fixed in 10.1.0.150
Interim mitigation

Update HUAWEI Mate 30 Pro to version 10.1.0.150(C00E136R5P3) or later to patch the face authentication validation flaw. Until updated, consider using alternative authentication methods (PIN, fingerprint) for sensitive operations.

Fix this in Mate 30 Pro Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1838 — 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-1838 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