dbcve.org
Mate 10 FirmwareOperating system · Huawei

CVE-2017-17227

HIGH · 7.8 CVSS v3.0 Published 2018-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
GPU driver in Huawei Mate 10 smart phones with the versions before ALP-L09 8.0.0.120(C212); The versions before ALP-L09 8.0.0.127(C900); The versions before ALP-L09 8.0.0.128(402/C02/C109/C346/C432/C652) has a out-of-bounds memory access vulnerability due to the input parameters validation. An attacker tricks a user into installing a malicious application on the smart phone, and the application can call the driver with special parameter and cause accessing out-of-bounds memory. Successful exploit may result in phone crash or arbitrary code execution.

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

The GPU driver in Huawei Mate 10 phones (ALP-L09 versions before 8.0.0.120/127/128) contains an out-of-bounds memory access vulnerability due to improper input validation. A malicious application can call the GPU driver with specially crafted parameters to trigger out-of-bounds memory access, potentially causing device crash or arbitrary code execution.

MitigationApply the vendor-supplied firmware update from Huawei that patches the GPU driver vulnerability. Users should avoid installing applications from untrusted sources to reduce exploit risk.

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
Mate 10 FirmwareOperating system
Affected:< alp-l09_8.0.0.120\(c212\)< alp-l09_8.0.0.127\(c900\)< alp-l09_8.0.0.128\(402\)< alp-l09_8.0.0.128\(c02\)< alp-l09_8.0.0.128\(c109\)< alp-l09_8.0.0.128\(c346\)< alp-l09_8.0.0.128\(c432\)< alp-l09_8.0.0.128\(c652\)

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

CVSS:3.0/AV:L/AC:L/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 device model
    Go to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell, to confirm the device is Huawei Mate 10 ALP-L09
    Affected if Device model is not ALP-L09 (this specific CVE affects only ALP-L09 variant)
  2. Check firmware version
    Go to Settings > About Phone > Version Number, or run 'getprop ro.build.version.emui' and 'getprop ro.build.display.id' via ADB shell
    Affected if Firmware version cannot be determined or is earlier than 8.0.0.120/127/128 depending on build variant
  3. Compare against affected version ranges
    Match your exact firmware build (such as ALP-L09 8.0.0.119 or earlier) against the affected version list: any version before 8.0.0.120(c212), 8.0.0.127(c900), or 8.0.0.128 variants (402, c02, c109, c346, c432, c652)
    Affected if Installed version is earlier than the listed thresholds for any of the three major branch versions (120, 127, or 128 families)
  4. Verify GPU driver is accessible
    On Android, the GPU driver is always active for rendering; no manual enablement needed. However, confirm device is not in a restricted execution environment by checking if third-party applications can run normally
    Affected if Device allows installation and execution of third-party applications (the attack vector requires a malicious app to call the GPU driver)

You are affected if your Huawei Mate 10 ALP-L09 runs firmware version earlier than 8.0.0.120(c212), 8.0.0.127(c900), or any 8.0.0.128 variant listed in the affected ranges.

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-supplied firmware update from Huawei that patches the GPU driver vulnerability. Users should avoid installing applications from untrusted sources to reduce exploit risk.

Fix this in Mate 10 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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