dbcve.org
Honor View 20 FirmwareOperating system · Huawei

CVE-2020-1808

HIGH · 7.1 CVSS v3.1 Published 2020-05-15
Fix available
A fix is available. Upgrade to 10.0.0.176 / 10.0.0.179 or later.
See remediation →
74/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
Honor 20;HONOR 20 PRO;Honor Magic2;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;Honor View 20 smartphones with versions earlier than 10.0.0.187(C00E60R4P11); versions earlier than 10.0.0.187(C00E60R4P11); versions earlier than 10.0.0.176(C00E60R2P11);9.1.0.135(C00E133R2P1); versions earlier than 10.1.0.123(C431E22R3P5), versions earlier than 10.1.0.126(C636E5R3P4), versions earlier than 10.1.0.160(C00E160R2P11); versions earlier than 10.1.0.126(C185E8R5P1), versions earlier than 10.1.0.126(C636E9R2P4), versions earlier than 10.1.0.160(C00E160R2P8); versions earlier than 10.0.0.179(C636E3R4P3), versions earlier than 10.0.0.180(C185E3R3P3), versions earlier than 10.0.0.180(C432E10R3P4), versions earlier than 10.0.0.181(C675E5R1P2) have an out of bound read vulnerability. The software reads data past the end of the intended buffer. The attacker tricks the user into installing a crafted application, successful exploit may cause information disclosure or service abnormal.

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 out-of-bounds read vulnerability in multiple Huawei/Honor smartphones (Honor 20 series, Magic2, Mate 20 X, P30 series, View 20). The vulnerability exists in the software that reads data past the end of the intended buffer, potentially exposing sensitive information from memory. Attackers must trick users into installing a crafted malicious application to trigger the vulnerability, which may result in information disclosure or service disruption.

MitigationApply vendor-provided firmware updates to affected devices (specific version thresholds listed per model). Organizations should enforce MDM policies restricting app installation to trusted sources and educate users about avoiding sideloaded applications.

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 View 20 FirmwareOperating system
Affected:< 10.0.0.179\(c636e3r4p3\)< 10.0.0.180\(c185e3r3p3\)< 10.0.0.180\(c432e10r3p4\)< 10.0.0.188\(c00e62r2p11\)
Honor 20 FirmwareOperating system
Affected:< 10.0.0.187\(c00e60r4p11\)
Honor 20 Pro FirmwareOperating system
Affected:< 10.0.0.187\(c00e60r4p11\)
Honor Magic2 FirmwareOperating system
Affected:< 10.0.0.176\(c00e60r2p11\)

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 your device model
    Go to Settings > About Phone on the device and note the model name
    Affected if The device is not one of: Honor View 20, Honor 20, Honor 20 Pro, or Honor Magic2 - these models are not affected
  2. Check Honor View 20 firmware version
    On Honor View 20, go to Settings > About Phone > Version and compare your build number against 10.0.0.179(c636e3r4p3), 10.0.0.180(c185e3r3p3), 10.0.0.180(c432e10r3p4), and 10.0.0.188(c00e62r2p11)
    Affected if Your firmware version is lower than ALL four listed threshold versions for View 20
  3. Check Honor 20 firmware version
    On Honor 20, go to Settings > About Phone > Version and compare your build number against 10.0.0.187(c00e60r4p11)
    Affected if Your firmware version is lower than 10.0.0.187(c00e60r4p11)
  4. Check Honor 20 Pro firmware version
    On Honor 20 Pro, go to Settings > About Phone > Version and compare your build number against 10.0.0.187(c00e60r4p11)
    Affected if Your firmware version is lower than 10.0.0.187(c00e60r4p11)
  5. Check Honor Magic2 firmware version
    On Honor Magic2, go to Settings > About Phone > Version and compare your build number against 10.0.0.176(c00e60r2p11)
    Affected if Your firmware version is lower than 10.0.0.176(c00e60r2p11)

You are affected if your device is an Honor View 20, Honor 20, Honor 20 Pro, or Honor Magic2 running a firmware version below the threshold listed for your specific 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.176 / 10.0.0.179 / 10.0.0.180 or later
Fixed in 10.0.0.17610.0.0.17910.0.0.180
Interim mitigation

Apply vendor-provided firmware updates to affected devices (specific version thresholds listed per model). Organizations should enforce MDM policies restricting app installation to trusted sources and educate users about avoiding sideloaded applications.

Fix this in Honor View 20 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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