dbcve.org
Mate 9 Pro FirmwareOperating system · Huawei

CVE-2017-17320

HIGH · 7.8 CVSS v3.0 Published 2018-03-20
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
Huawei Mate 9 Pro smartphones with software of LON-AL00BC00B139D, LON-AL00BC00B229, LON-L29DC721B188 have a memory double free vulnerability. The system does not manage the memory properly, that frees on the same memory address twice. An attacker tricks the user who has root privilege to install a crafted application, successful exploit could result in malicious 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

A memory double-free vulnerability exists in Huawei Mate 9 Pro smartphones (software versions LON-AL00BC00B139D, LON-AL00BC00B229, LON-L29DC721B188). The system incorrectly frees the same memory address twice, leading to potential memory corruption. Exploitation requires a root-privileged user to install a crafted malicious application, which could result in arbitrary code execution.

MitigationApply vendor-supplied firmware patches from Huawei for the affected software versions. Until patched, enforce policies prohibiting installation of untrusted applications on devices with root privileges.

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 9 Pro FirmwareOperating system
Affected:= lon-al00bc00b139d= lon-al00bc00b229= lon-l29dc721b188

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. Confirm device model is Huawei Mate 9 Pro
    Check the device settings: go to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell
    Affected if Model number is not Huawei Mate 9 Pro (the vulnerability only affects this specific device)
  2. Check installed firmware version
    Go to Settings > About Phone > Build Number, or run 'getprop ro.build.display.id' via ADB shell. Compare the displayed version against the affected builds: LON-AL00BC00B139D, LON-AL00BC00B229, LON-L29DC721B188
    Affected if The firmware version exactly matches one of these three builds: LON-AL00BC00B139D, LON-AL00BC00B229, or LON-L29DC721B188
  3. Verify root privilege status
    Check if the device has root access by using a root checker app or running 'su' via ADB shell. Also inspect if Superuser/SuperSU apps are installed
    Affected if Root privileges are enabled or the device has been rooted, because exploitation requires a root-privileged user to install the malicious application
  4. Review application installation policy
    Check device security settings: go to Settings > Security > Unknown Sources (or Settings > Apps > Special Access > Install Unknown Apps) to see if installation of apps from unknown sources is permitted
    Affected if Installation of untrusted applications is allowed on a rooted device running an affected firmware version, creating the complete exploitation path

A user is affected if they have a Huawei Mate 9 Pro running firmware version LON-AL00BC00B139D, LON-AL00BC00B229, or LON-L29DC721B188 AND the device has root privileges, allowing a malicious app to trigger the double-free vulnerability.

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 vendor-supplied firmware patches from Huawei for the affected software versions. Until patched, enforce policies prohibiting installation of untrusted applications on devices with root privileges.

Fix this in Mate 9 Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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