dbcve.org
Mate 10 Pro FirmwareOperating system · Huawei

CVE-2020-1785

MEDIUM · 5.5 CVSS v3.1 Published 2020-01-03
Fix available
A fix is available. Upgrade to 9.1.0.225 / 9.1.0.321 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
Mate 10 Pro;Honor V10;Honor 10;Nova 4 smartphones have a denial of service vulnerability. The system does not properly check the status of certain module during certain operations, an attacker should trick the user into installing a malicious application, successful exploit could cause reboot of the smartphone.

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

A denial of service vulnerability exists in certain Huawei smartphones (Mate 10 Pro, Honor V10, Honor 10, Nova 4) where the system fails to properly check the status of a certain module during specific operations. An attacker can exploit this by tricking the user into installing a malicious application, which triggers a condition causing the smartphone to reboot.

MitigationUsers should avoid installing applications from untrusted sources and ensure device firmware is updated to the latest version provided by Huawei. Organizations should implement mobile device management (MDM) policies to restrict app installations.

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 10 Pro FirmwareOperating system
Affected:< 9.1.0.321\(c605e4r1p13t8\)< 9.1.0.321\(c636e4r1p14t8\)< 9.1.0.330\(c432e6r1p12t8\)
Honor V10 FirmwareOperating system
Affected:< 9.1.0.333\(c00e333r2p1t8\)< 9.1.0.350\(c636e4r1p13t8\)< 9.1.0.351\(c432e5r1p13t8\)
Honor 10 FirmwareOperating system
Affected:< 9.1.0.350\(c10e5r1p14t8\)< 9.1.0.350\(c185e3r1p12t8\)< 9.1.0.350\(c461e3r1p11t8\)< 9.1.0.350\(c636e3r1p13t8\)< 9.1.0.351\(c432e5r1p13t8\)
Nova 4 FirmwareOperating system
Affected:< 9.1.0.225\(c636e1r4p1\)

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
    Check the phone settings to confirm the exact model (Settings > About Phone > Model)
    Affected if Model is not Mate 10 Pro, Honor V10, Honor 10, or Nova 4 - these are the only affected models
  2. Check Mate 10 Pro firmware version
    Go to Settings > About Phone > Version, look for build number starting with c605e4, c636e4, or c432e6
    Affected if Firmware version is below 9.1.0.321 for c605e4/c636e4 builds, or below 9.1.0.330 for c432e6 build
  3. Check Honor V10 firmware version
    Go to Settings > About Phone > Version, look for build number starting with c00e333, c636e4, or c432e5
    Affected if Firmware version is below 9.1.0.333 (c00e333), below 9.1.0.350 (c636e4), or below 9.1.0.351 (c432e5)
  4. Check Honor 10 firmware version
    Go to Settings > About Phone > Version, look for build number starting with c10e5, c185e3, c461e3, c636e3, or c432e5
    Affected if Firmware version is below 9.1.0.350 for c10e5/c185e3/c461e3/c636e3 builds, or below 9.1.0.351 for c432e5 build
  5. Check Nova 4 firmware version
    Go to Settings > About Phone > Version, look for build number starting with c636e1
    Affected if Firmware version is below 9.1.0.225 for c636e1 build

Device is affected only if it is one of the four listed models AND its firmware version is below the specific version thresholds for its build number prefix.

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.225 / 9.1.0.321 / 9.1.0.330 or later
Fixed in 9.1.0.2259.1.0.3219.1.0.330
Interim mitigation

Users should avoid installing applications from untrusted sources and ensure device firmware is updated to the latest version provided by Huawei. Organizations should implement mobile device management (MDM) policies to restrict app installations.

Fix this in Mate 10 Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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