dbcve.org
Mate 20 FirmwareOperating system · Huawei

CVE-2020-9244

MEDIUM · 6.8 CVSS v3.1 Published 2020-08-11
Fix available
A fix is available. Upgrade to 10.0.0.175 / 10.0.0.187 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 versions Versions earlier than 10.1.0.160(C00E160R3P8);HUAWEI Mate 20 Pro versions Versions earlier than 10.1.0.270(C431E7R1P5),Versions earlier than 10.1.0.270(C635E3R1P5),Versions earlier than 10.1.0.273(C636E7R2P4);HUAWEI Mate 20 X versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI P30 versions Versions earlier than 10.1.0.160(C00E160R2P11);HUAWEI P30 Pro versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI Mate 20 RS versions Versions earlier than 10.1.0.160(C786E160R3P8);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);Honor20 versions Versions earlier than 10.0.0.175(C00E58R4P11);Honor20 PRO versions Versions earlier than 10.0.0.194(C00E62R8P12);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);HonorV20 versions Versions earlier than 10.0.0.188(C00E62R2P11) have an improper authentication vulnerability. The system does not properly sign certain encrypted file, the attacker should gain the key used to encrypt the file, successful exploit could cause certain file be forged

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

The vulnerability exists in the file encryption/signing mechanism of affected Huawei devices. The system does not properly sign certain encrypted files, allowing an attacker who obtains the encryption key to forge files. This is an authentication/integrity weakness with CVSS 6.8 indicating moderate exploitability.

MitigationApply the vendor-provided firmware updates that address this vulnerability for each affected device model and variant listed.

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:< 10.1.0.160\(c00e160r3p8\)
Mate 20 Pro FirmwareOperating system
Affected:< 10.1.0.270\(c431e7r1p5\)< 10.1.0.270\(c635e3r1p5\)< 10.1.0.273\(c636e7r2p4\)
Mate 20 X FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p8\)
P30 FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p11\)
P30 Pro FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p8\)
Mate 20 Rs FirmwareOperating system
Affected:< 10.1.0.160\(c786e160r3p8\)
Honor Magic 2 FirmwareOperating system
Affected:< 10.0.0.187\(c00e61r2p11\)
Honor 20 FirmwareOperating system
Affected:< 10.0.0.175\(c00e58r4p11\)

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/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. Identify your Huawei device model
    Check the device settings under Settings > About Phone > Model to confirm it is one of: Mate 20, Mate 20 Pro, Mate 20 X, P30, P30 Pro, Mate 20 Rs, Honor Magic 2, or Honor 20
    Affected if The device model is NOT one of the listed affected models (you are not affected)
  2. Check Mate 20 firmware version
    Navigate to Settings > About Phone > Version > Build Number. Compare the version number against the affected thresholds: Mate 20 requires 10.1.0.160(c00e160r3p8) or higher
    Affected if The firmware version is lower than 10.1.0.160(c00e160r3p8)
  3. Check Mate 20 Pro firmware version
    Navigate to Settings > About Phone > Version > Build Number. Compare the version number against the affected thresholds: 10.1.0.270(c431e7r1p5), 10.1.0.270(c635e3r1p5), or 10.1.0.273(c636e7r2p4) or higher
    Affected if The firmware version is lower than any of the three threshold versions listed for your variant
  4. Check Mate 20 X firmware version
    Navigate to Settings > About Phone > Version > Build Number. Compare the version number against the affected threshold: 10.1.0.160(c00e160r2p8)
    Affected if The firmware version is lower than 10.1.0.160(c00e160r2p8)
  5. Check P30/P30 Pro firmware version
    Navigate to Settings > About Phone > Version > Build Number. Compare the version number against the affected thresholds: P30 requires 10.1.0.160(c00e160r2p11) or higher, P30 Pro requires 10.1.0.160(c00e160r2p8) or higher
    Affected if The firmware version is lower than the specified threshold for your model
  6. Check Honor device firmware version
    Navigate to Settings > About Phone > Version > Build Number. Compare: Honor Magic 2 requires 10.0.0.187(c00e61r2p11) or higher, Honor 20 requires 10.0.0.175(c00e58r4p11) or higher
    Affected if The firmware version is lower than the specified threshold for your Honor model

You are affected if your device model is Mate 20, Mate 20 Pro, Mate 20 X, P30, P30 Pro, Mate 20 Rs, Honor Magic 2, or Honor 20 AND your firmware version is below the corresponding threshold listed for that model.

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.175 / 10.0.0.187 / 10.1.0.160 or later
Fixed in 10.0.0.17510.0.0.18710.1.0.160
Interim mitigation

Apply the vendor-provided firmware updates that address this vulnerability for each affected device model and variant listed.

Fix this in Mate 20 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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