dbcve.org
P20 Pro FirmwareOperating system · Huawei

CVE-2019-5230

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
P20 Pro, P20, Mate RS smartphones with versions earlier than Charlotte-AL00A 9.1.0.321(C00E320R1P1T8), versions earlier than Emily-AL00A 9.1.0.321(C00E320R1P1T8), versions earlier than NEO-AL00D NEO-AL00 9.1.0.321(C786E320R1P1T8) have an improper validation vulnerability. The system does not perform a properly validation of certain input models, an attacker could trick the user to install a malicious application then craft a malformed model, successful exploit could allow the attacker to get and tamper certain output data information.

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

This is an input validation vulnerability in Huawei P20 Pro, P20, and Mate RS smartphones where the system fails to properly validate certain input models. An attacker tricks a user into installing a malicious application, which then crafts malformed models to exploit the improper validation, allowing unauthorized access to and tampering of certain output data.

MitigationUpdate affected smartphone models to version 9.1.0.321(C00E320R1P1T8) or later for Charlotte-AL00A and Emily-AL00A variants, and version 9.1.0.321(C786E320R1P1T8) or later for NEO-AL00D and NEO-AL00 variants.

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
P20 Pro FirmwareOperating system
Affected:< charlotte-al00a_9.1.0.321\(c00e320r1p1t8\)
P20 FirmwareOperating system
Affected:< emily-al00a_9.1.0.321\(c00e320r1p1t8\)
Mate Rs FirmwareOperating system
Affected:< neo-al00d_neo-al00_9.1.0.321\(c786e320r1p1t8\)

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 smartphone model
    Check the device settings: Go to Settings > About Phone > Model Name to confirm the device is a Huawei P20 Pro, P20, or Mate RS.
    Affected if Device model is not one of these three models, then the CVE does not apply.
  2. Locate firmware version in settings
    On the device, navigate to Settings > About Phone > Version. Record the Build Number or Firmware Version displayed.
    Affected if The displayed version is the only indicator available for comparison.
  3. Check P20 Pro firmware version
    For Huawei P20 Pro (Charlotte-AL00A variant), compare your Build Number against charlotte-al00a_9.1.0.321(c00e320r1p1t8). This is typically shown in Settings > About Phone > Version > Build Number.
    Affected if If the build number is lower than c00e320r1p1t8 (or the version string is lexicographically earlier than charlotte-al00a_9.1.0.321), the device is affected.
  4. Check P20 firmware version
    For Huawei P20 (Emily-AL00A variant), compare your Build Number against emily-al00a_9.1.0.321(c00e320r1p1t8). This is typically shown in Settings > About Phone > Version > Build Number.
    Affected if If the build number is lower than c00e320r1p1t8 (or the version string is lexicographically earlier than emily-al00a_9.1.0.321), the device is affected.
  5. Check Mate RS firmware version
    For Huawei Mate RS (NEO-AL00D or NEO-AL00 variants), compare your Build Number against neo-al00d_neo-al00_9.1.0.321(c786e320r1p1t8). This is typically shown in Settings > About Phone > Version > Build Number.
    Affected if If the build number is lower than c786e320r1p1t8 (or the version string is lexicographically earlier than neo-al00d_neo-al00_9.1.0.321), the device is affected.

The device is affected only if it is a Huawei P20 Pro, P20, or Mate RS with firmware version lower than 9.1.0.321(C00E320R1P1T8) for P20 Pro/P20, or lower than 9.1.0.321(C786E320R1P1T8) for Mate RS.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected smartphone models to version 9.1.0.321(C00E320R1P1T8) or later for Charlotte-AL00A and Emily-AL00A variants, and version 9.1.0.321(C786E320R1P1T8) or later for NEO-AL00D and NEO-AL00 variants.

Fix this in P20 Pro Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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