dbcve.org
P30 FirmwareOperating system · Huawei

CVE-2020-1800

HIGH · 7.8 CVSS v3.1 Published 2020-03-26
Fix available
A fix is available. Upgrade to 10.0.0.185 or later.
See remediation →
81/100
Remediation priority · High
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 smartphones P30 with versions earlier than 10.0.0.185(C00E85R1P11) have an improper access control vulnerability. The software incorrectly restricts access to a function interface from an unauthorized actor, the attacker tricks the user into installing a crafted application, successful exploit could allow the attacker do certain unauthenticated operations.

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 · moderate confidence

Improper access control vulnerability in HUAWEI P30 smartphones allows a crafted application to bypass authentication and access function interfaces that should be restricted. The attacker tricks the user into installing the malicious application, which can then perform unauthenticated operations.

MitigationUpdate HUAWEI P30 to version 10.0.0.185(C00E85R1P11) or later. Avoid installing applications from untrusted sources.

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
P30 FirmwareOperating system
Affected:< 10.0.0.185\(c00e85r1p11\)

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify device model
    Go to Settings > About Phone > Model Name, or check the device physical label, to confirm it is a HUAWEI P30
    Affected if Device is not a HUAWEI P30 (not affected by this specific vulnerability)
  2. Check firmware version number
    Go to Settings > About Phone > Version > Build Number, or dial *#*#2846579#*#* to access engineering menu, then check the SW version
    Affected if Firmware version is 10.0.0.185(c00e85r1p11) or higher (not affected); version is below 10.0.0.185(c00e85r1p11) (potentially affected)
  3. Verify if installation from untrusted sources is permitted
    Go to Settings > Apps > Menu (three dots) > Special access > Install unknown apps, or check Settings > Security > Unknown sources, to see which applications can install other apps
    Affected if Unknown sources/Install unknown apps is enabled for any application (allows the attack vector to work)

Device is affected if it is a HUAWEI P30 running firmware version below 10.0.0.185(c00e85r1p11) AND has the ability to install applications from untrusted sources 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 10.0.0.185 or later
Fixed in 10.0.0.185
Interim mitigation

Update HUAWEI P30 to version 10.0.0.185(C00E85R1P11) or later. Avoid installing applications from untrusted sources.

Fix this in P30 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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