P20 FirmwareOperating system · Huawei

CVE-2019-5211

MEDIUM · 5.7 CVSS v3.1 Published 2019-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
The Huawei Share function of P20 phones with versions earlier than Emily-L29C 9.1.0.311 has an improper file management vulnerability. The attacker tricks the victim to perform certain operations on the mobile phone during file transfer. Because the file is not properly processed, successfully exploit may cause some files on the victim's mobile phone are deleted.

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

The Huawei Share function in P20 phones versions earlier than Emily-L29C 9.1.0.311 has an improper file management vulnerability. During file transfer, files are not properly processed, allowing an attacker who tricks the victim into performing certain operations during the transfer to cause deletion of some files on the victim's device.

MitigationUpdate Huawei P20 devices to version Emily-L29C 9.1.0.311 or later to receive the proper file handling fix. Users should avoid performing untrusted operations during Huawei Share file transfers.

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 FirmwareOperating system
Affected:< emily-l29c_9.1.0.311\(c10e2r1p13t8\)< emily-l29c_9.1.0.311\(c461e2r1p11t8\)< emily-l29c_9.1.0.311\(c605e2r1p12t8\)< emily-l29c_9.1.0.311\(c432e7r1p11t8\)

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

CVSS:3.1/AV:A/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. Confirm device model is Huawei P20
    Go to Settings > About Phone > Model Number (or Device name) and verify the device is Huawei P20
    Affected if Device is not a Huawei P20 model, then not affected by this specific CVE
  2. Check current firmware version
    Go to Settings > About Phone > Version > Build Number. Look for a build number that starts with one of: emily-l29c_9.1.0.311(c10e2r1p13t8), emily-l29c_9.1.0.311(c461e2r1p11t8), emily-l29c_9.1.0.311(c605e2r1p12t8), or emily-l29c_9.1.0.311(c432e7r1p11t8)
    Affected if Build number matches any of these four specific builds and is earlier than 9.1.0.311 in the full version string
  3. Determine if firmware version is vulnerable
    Compare the full firmware version string to the affected threshold: emily-L29C 9.1.0.311. Any version number lower than 9.1.0.311 in the emily-L29C variant is potentially affected.
    Affected if Installed version is less than Emily-L29C 9.1.0.311 (for example, 9.1.0.300, 9.0.0.150, etc.)
  4. Verify Huawei Share feature usage
    Check if Huawei Share (or Huawei Share OneHop) feature is enabled on the device: Go to Settings > Device Connectivity > Huawei Share, or swipe down from the top of the screen to see if Huawei Share quick toggle is present
    Affected if Huawei Share feature is enabled or frequently used, making exploitation possible during file transfers

User is affected if they have a Huawei P20 with firmware version earlier than Emily-L29C 9.1.0.311 and actively use the Huawei Share feature for file transfers.

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 Huawei P20 devices to version Emily-L29C 9.1.0.311 or later to receive the proper file handling fix. Users should avoid performing untrusted operations during Huawei Share file transfers.

Fix this in P20 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-5211 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