dbcve.org
Honor 20 Pro FirmwareOperating system · Huawei

CVE-2020-9235

MEDIUM · 5.5 CVSS v3.1 Published 2020-09-03
Fix available
A fix is available. Upgrade to 10.1.0.160 / 10.1.0.212 or later.
See remediation →
57/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 smartphones HONOR 20 PRO Versions earlier than 10.1.0.230(C432E9R5P1),Versions earlier than 10.1.0.231(C10E3R3P2),Versions earlier than 10.1.0.231(C185E3R5P1),Versions earlier than 10.1.0.231(C636E3R3P1);Versions earlier than 10.1.0.212(C432E10R3P4),Versions earlier than 10.1.0.213(C636E3R4P3),Versions earlier than 10.1.0.214(C10E5R4P3),Versions earlier than 10.1.0.214(C185E3R3P3);Versions earlier than 10.1.0.212(C00E210R5P1);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C01E160R2P11);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C00E160R8P12);Versions earlier than 10.1.0.230(C432E9R5P1),Versions earlier than 10.1.0.231(C10E3R3P2),Versions earlier than 10.1.0.231(C636E3R3P1);Versions earlier than 10.1.0.225(C431E3R1P2),Versions earlier than 10.1.0.225(C432E3R1P2) contain an information vulnerability. A module has a design error that is lack of control of input. Attackers can exploit this vulnerability to obtain some information. This can lead to information leak.

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 module in HONOR 20 PRO smartphones contains an information disclosure vulnerability due to a design error lacking proper input control. Attackers can exploit this to obtain sensitive information through unspecified attack vectors, likely involving crafted input to an affected module.

MitigationApply the vendor-provided firmware updates (10.1.0.230 for C432E9R5P1, 10.1.0.231 for C10E3R3P2/C636E3R3P1/C185E3R5P1, and corresponding versions for other builds) to patched versions.

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
Honor 20 Pro FirmwareOperating system
Affected:< 10.1.0.230\(c432e9r5p1\)< 10.1.0.231\(c10e3r3p2\)< 10.1.0.231\(c185e3r5p1\)< 10.1.0.231\(c636e3r3p1\)
Honor View 20 FirmwareOperating system
Affected:< 10.1.0.212\(c432e10r3p4\)< 10.1.0.213\(c636e3r4p3\)< 10.1.0.214\(c10e5r4p3\)< 10.1.0.214\(c185e3r3p3\)
Oxfords An00a FirmwareOperating system
Affected:< 10.1.0.212\(c00e210r5p1\)
Princeton Al10b FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p11\)
Princeton Al10d FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p11\)
Princeton Tl10c FirmwareOperating system
Affected:< 10.1.0.160\(c01e160r2p11\)
Tony Al00b FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r2p11\)
Yale Al00a FirmwareOperating system
Affected:< 10.1.0.160\(c00e160r8p12\)

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify your device model
    Go to Settings > About Phone > Model Name (or Device name) and verify it matches one of these affected models: Honor 20 Pro, Honor View 20, Oxford (An00a), Princeton (Al10b, Al10d, Tl10c), Tony (Al00b), or Yale (Al00a)
    Affected if Device model is not one of the listed affected models, then not vulnerable
  2. Locate firmware version information
    Go to Settings > About Phone > Version. Look for the build number displayed (typically shows as something like 10.1.0.xxx with a suffix in parentheses)
    Affected if Cannot access version information through standard Android settings
  3. Determine your specific build variant
    In Settings > About Phone > Build Number or Software Version, identify the full build identifier which includes the alphanumeric suffix (for example: C432E9R5P1, C10E3R3P2, C185E3R5P1, C636E3R3P1, or similar)
    Affected if Build suffix cannot be determined from the device settings
  4. Compare version against affected ranges for Honor 20 Pro
    If the device is Honor 20 Pro, check if the firmware version is lower than 10.1.0.230 with suffix C432E9R5P1, OR lower than 10.1.0.231 with any of these suffixes: C10E3R3P2, C185E3R5P1, C636E3R3P1
    Affected if Firmware version matches or exceeds all four listed version thresholds for Honor 20 Pro, then likely not vulnerable
  5. Compare version against affected ranges for Honor View 20
    If the device is Honor View 20, check if firmware is lower than 10.1.0.212(C432E10R3P4), lower than 10.1.0.213(C636E3R4P3), or lower than 10.1.0.214 with suffixes C10E5R4P3 or C185E3R3P3
    Affected if Firmware version matches or exceeds all four listed version thresholds for Honor View 20, then likely not vulnerable
  6. Compare version against affected ranges for other Huawei models
    For Oxford An00a, check < 10.1.0.212(C00E210R5P1). For Princeton Al10b/Al10d, Princeton Tl10c, Tony Al00b, and Yale Al00a, check < 10.1.0.160 with their respective suffixes as listed in the affected versions
    Affected if Firmware version meets or exceeds the listed threshold for that specific model, then likely not vulnerable

The device is affected if it is one of the listed Honor/Huawei models AND its firmware version (including build suffix) is lower than the specified threshold version 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.1.0.160 / 10.1.0.212 / 10.1.0.213 or later
Fixed in 10.1.0.16010.1.0.21210.1.0.213
Interim mitigation

Apply the vendor-provided firmware updates (10.1.0.230 for C432E9R5P1, 10.1.0.231 for C10E3R3P2/C636E3R3P1/C185E3R5P1, and corresponding versions for other builds) to patched versions.

Fix this in Honor 20 Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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