dbcve.org
Mate 10 FirmwareOperating system · Huawei

CVE-2017-15311

HIGH · 8.8 CVSS v3.0 Published 2017-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 baseband modules of Mate 10, Mate 10 Pro, Mate 9, Mate 9 Pro Huawei smart phones with software before ALP-AL00 8.0.0.120(SP2C00), before BLA-AL00 8.0.0.120(SP2C00), before MHA-AL00B 8.0.0.334(C00), and before LON-AL00B 8.0.0.334(C00) have a stack overflow vulnerability due to the lack of parameter validation. An attacker could send malicious packets to the smart phones within radio range by special wireless device, which leads stack overflow when the baseband module handles these packets. The attacker could exploit this vulnerability to perform a denial of service attack or remote code execution in baseband module.

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

Stack overflow vulnerability in Huawei smartphone baseband modules (Mate 9/10 series) due to missing parameter validation. Attackers within radio range can send specially crafted malicious packets to trigger stack overflow, potentially achieving remote code execution or denial of service in the baseband processor.

MitigationApply vendor firmware updates (ALP-AL00 8.0.0.120(SP2C00), BLA-AL00 8.0.0.120(SP2C00), MHA-AL00B 8.0.0.334(C00), LON-AL00B 8.0.0.334(C00) or later) to affected devices. Until patched, limit exposure by avoiding untrusted wireless environments.

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-al00_8.0.0.120\(sp2c00\)
Mate 10 Pro FirmwareOperating system
Affected:< bla-al00_8.0.0.120\(sp2c00\)
Mate 9 FirmwareOperating system
Affected:< mha-al00b_8.0.0.334\(c00\)
Mate 9 Pro FirmwareOperating system
Affected:< lon-al00b_8.0.0.334\(c00\)

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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
    Check the device model in Settings > About Phone > Model or look at the device packaging/label. Confirm it is one of: Huawei Mate 9, Mate 9 Pro, Mate 10, or Mate 10 Pro.
    Affected if Device is NOT one of these four models, then not affected by this specific CVE.
  2. Check firmware version for Mate 10
    Navigate to Settings > About Phone > Version (or Settings > System > About Device > Version). Look for the build number that starts with 'alp-al00' or 'bla-al00' (Mate 10 or Mate 10 Pro respectively).
    Affected if Version starts with alp-al00 and is LOWER than 8.0.0.120(sp2c00), OR starts with bla-al00 and is LOWER than 8.0.0.120(sp2c00).
  3. Check firmware version for Mate 9
    Navigate to Settings > About Phone > Version (or Settings > System > About Device > Version). Look for the build number that starts with 'mha-al00b' or 'lon-al00b' (Mate 9 or Mate 9 Pro respectively).
    Affected if Version starts with mha-al00b and is LOWER than 8.0.0.334(c00), OR starts with lon-al00b and is LOWER than 8.0.0.334(c00).
  4. Confirm baseband vulnerability context
    This flaw requires the baseband radio processor to be active and reachable. The vulnerability is triggered by specially crafted packets received over the cellular radio interface. No user action beyond normal phone operation is required for the attack surface to exist.
    Affected if The device has cellular connectivity enabled and is within radio range of an attacker - this is the default state for smartphones.

If your device is a Mate 9, Mate 9 Pro, Mate 10, or Mate 10 Pro AND the firmware version is below the thresholds listed (8.0.0.120 for Mate 10 series, 8.0.0.334 for Mate 9 series), then your device is affected by this CVE.

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 firmware updates (ALP-AL00 8.0.0.120(SP2C00), BLA-AL00 8.0.0.120(SP2C00), MHA-AL00B 8.0.0.334(C00), LON-AL00B 8.0.0.334(C00) or later) to affected devices. Until patched, limit exposure by avoiding untrusted wireless environments.

Fix this in Mate 10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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