dbcve.org
Honor View 10 FirmwareOperating system · Huawei

CVE-2019-5216

HIGH · 7.0 CVSS v3.0 Published 2019-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
There is a race condition vulnerability on Huawei Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.156(C00E156R2P14T8), Honor 10 smartphones versions earlier than Columbia-AL10B 9.0.0.156(C00E156R1P20T8) and Honor Play smartphones versions earlier than Cornell-AL00A 9.0.0.156(C00E156R1P13T8). An attacker tricks the user into installing a malicious application, which makes multiple processes to operate the same variate at the same time. Successful exploit could cause execution of malicious code.

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

A race condition vulnerability exists in Huawei Honor V10, Honor 10, and Honor Play smartphones where a malicious application can trigger multiple processes to simultaneously operate on the same shared variable, leading to potential arbitrary code execution. The vulnerability stems from improper synchronization in the kernel or system services when handling concurrent operations on shared memory. User interaction is required (installation of malicious app) for exploitation.

MitigationApply the vendor-provided firmware update (Berkeley-AL20 9.0.0.156(C00E156R2P14T8) or later for V10, Columbia-AL10B 9.0.0.156(C00E156R1P20T8) or later for Honor 10, Cornell-AL00A 9.0.0.156(C00E156R1P13T8) or later for Honor Play). Additionally, enforce application installation policies to prevent installation from untrusted sources.

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 10 FirmwareOperating system
Affected:< berkeley-al20_9.0.0.156\(c00e156r2p14t8\)
Honor 10 FirmwareOperating system
Affected:< columbia-al10b_9.0.0.156\(c00e156r1p20t8\)
Honor Play FirmwareOperating system
Affected:< cornell-al00a_9.0.0.156\(c00e156r1p13t8\)

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

CVSS:3.0/AV:L/AC:H/PR:N/UI:R/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 the device model
    Go to Settings > About Phone on the Huawei/Honor device and note the exact model name (look for Honor View 10, Honor 10, or Honor Play)
    Affected if The device is not one of these three models (Honor View 10, Honor 10, or Honor Play)
  2. Check firmware version for Honor View 10
    In Settings > About Phone > Version, look for the build number that contains 'berkeley-al20' followed by the version string (for example: berkeley-al20_9.0.0.XXX)
    Affected if The device is an Honor View 10 and the version is earlier than 9.0.0.156(c00e156r2p14t8)
  3. Check firmware version for Honor 10
    In Settings > About Phone > Version, look for the build number that contains 'columbia-al10b' followed by the version string (for example: columbia-al10b_9.0.0.XXX)
    Affected if The device is an Honor 10 and the version is earlier than 9.0.0.156(c00e156r1p20t8)
  4. Check firmware version for Honor Play
    In Settings > About Phone > Version, look for the build number that contains 'cornell-al00a' followed by the version string (for example: cornell-al00a_9.0.0.XXX)
    Affected if The device is an Honor Play and the version is earlier than 9.0.0.156(c00e156r1p13t8)

The device is affected if it is an Honor View 10, Honor 10, or Honor Play running firmware below the respective version threshold (9.0.0.156 with the appropriate build identifier for each 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided firmware update (Berkeley-AL20 9.0.0.156(C00E156R2P14T8) or later for V10, Columbia-AL10B 9.0.0.156(C00E156R1P20T8) or later for Honor 10, Cornell-AL00A 9.0.0.156(C00E156R1P13T8) or later for Honor Play). Additionally, enforce application installation policies to prevent installation from untrusted sources.

Fix this in Honor View 10 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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