dbcve.org
Mate 7 FirmwareOperating system · Huawei

CVE-2015-8337

MEDIUM · 5.5 CVSS v3.0 Published 2016-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/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 HIFI driver in Huawei P8 phones with software GRA-TL00 before GRA-TL00C01B220SP01, GRA-CL00 before GRA-CL00C92B220, GRA-CL10 before GRA-CL10C92B220, GRA-UL00 before GRA-UL00C00B220, GRA-UL10 before GRA-UL10C00B220 and Mate7 phones with software MT7-UL00 before MT7-UL00C17B354, MT7-TL10 before MT7-TL10C00B354, MT7-TL00 before MT7-TL00C01B354, and MT7-CL00 before MT7-CL00C92B354 allows remote attackers to cause a denial of service (invalid memory access and reboot) via unspecified vectors related to "input null pointer as parameter."

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 HIFI driver in Huawei P8 and Mate7 phones contains a null pointer dereference vulnerability that allows remote attackers to cause a denial of service by passing invalid input (null pointer) as a parameter, resulting in invalid memory access and device reboot.

MitigationApply the vendor-supplied firmware updates for the specific build numbers listed (e.g., GRA-TL00C01B220SP01 for P8, MT7-UL00C17B354 for Mate7). If devices cannot be updated, consider network-based controls to limit exposure and replacement of affected devices.

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 7 FirmwareOperating system
Affected:= mt7-cl00= mt7-tl00= mt7-tl10= mt7-ul00
P8 FirmwareOperating system
Affected:= gra-cl10= gra-cl100= gra-tl00= gra-ul10= gra-ul100

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 physical device or system settings to confirm whether the device is a Huawei P8 or Huawei Mate 7. On Android, go to Settings > About Phone > Model Number.
    Affected if The device model is NOT one of: P8 (any variant) or Mate 7 (any variant). If the device is neither P8 nor Mate 7, it is not affected.
  2. Check P8 firmware version
    On the Huawei P8, go to Settings > About Phone > Version. Look for the build number (e.g., GRA-TL00C01B220SP01). This is typically displayed as a code like gra-xx, where xx represents the region/carrier variant.
    Affected if The device IS a Huawei P8 AND the firmware identifier starts with any of: gra-cl10, gra-cl100, gra-tl00, gra-ul10, or gra-ul100.
  3. Check Mate 7 firmware version
    On the Huawei Mate 7, go to Settings > About Phone > Version. Look for the build number (e.g., MT7-UL00C17B354). This is typically displayed as a code like mt7-xx, where xx represents the region/carrier variant.
    Affected if The device IS a Huawei Mate 7 AND the firmware identifier starts with any of: mt7-cl00, mt7-tl00, mt7-tl10, or mt7-ul00.
  4. Verify HIFI driver is accessible
    This vulnerability exists in the HIFI audio driver component. On affected firmware versions, the driver handles audio processing and is active by default on these devices. No special configuration needs to be checked - the vulnerability is present if the firmware version matches.
    Affected if The device runs an affected firmware version listed above. The HIFI driver is included in the stock firmware and requires no user enablement.

A device is affected if it is a Huawei P8 or Mate 7 running firmware identifiers matching the specific model codes (gra-xxx for P8, mt7-xxx for Mate 7) listed in the affected versions.

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 updates for the specific build numbers listed (e.g., GRA-TL00C01B220SP01 for P8, MT7-UL00C17B354 for Mate7). If devices cannot be updated, consider network-based controls to limit exposure and replacement of affected devices.

Fix this in Mate 7 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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