dbcve.org
Mate S FirmwareOperating system · Huawei

CVE-2016-8792

HIGH · 7.1 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 8 phones with software Versions before NXT-AL10C00B386, Versions before NXT-CL00C92B386, Versions before NXT-DL00C17B386, Versions before NXT-TL00C01B386; Mate S phones with software Versions before CRR-CL00C92B368, Versions before CRR-CL20C92B368, Versions before CRR-TL00C01B368, Versions before CRR-UL00C00B368, Versions before CRR-UL20C00B368; and P8 phones with software Versions before GRA-TL00C01B366, Versions before GRA-CL00C92B366, Versions before GRA-CL10C92B366, Versions before GRA-UL00C00B366, Versions before GRA-UL10C00B366 allow attackers with graphic or Camera privilege to crash the system or escalate privilege.

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 · moderate confidence

This is a privilege escalation vulnerability in Huawei's graphics/camera subsystem affecting Mate 8, Mate S, and P8 phones. Attackers with graphic or Camera privilege can exploit this to crash the system or escalate to higher privileges, likely by leveraging improper input validation or permission checks in the camera/graphics driver.

MitigationUpdate affected devices to the specified software versions (NXT-AL10C00B386 or later for Mate 8, CRR-CL00C92B368 or later for Mate S, GRA-TL00C01B366 or later for P8) to receive the security patch.

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 S FirmwareOperating system
Affected:all versions
Mate 8 FirmwareOperating system
Affected:all versions
P8 FirmwareOperating system
Affected:all versions

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

CVSS:3.0/AV:N/AC:H/PR:L/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 your device model
    Check Settings > About Phone or run 'adb shell getprop ro.product.model' to confirm the exact model number
    Affected if Model is not Huawei Mate 8, Mate S, or P8 (these are the only affected models)
  2. Check Mate 8 firmware version
    Go to Settings > About Phone > Version, or run 'adb shell getprop ro.build.version.emui' and 'adb shell getprop ro.build.version.incremental' to see the exact firmware build
    Affected if Device is Huawei Mate 8 and firmware version is earlier than NXT-AL10C00B386 (all versions are affected before this fix)
  3. Check Mate S firmware version
    Go to Settings > About Phone > Version, or run 'adb shell getprop ro.build.version.emui' and 'adb shell getprop ro.build.version.incremental' to see the exact firmware build
    Affected if Device is Huawei Mate S and firmware version is earlier than CRR-CL00C92B368 (all versions are affected before this fix)
  4. Check P8 firmware version
    Go to Settings > About Phone > Version, or run 'adb shell getprop ro.build.version.emui' and 'adb shell getprop ro.build.version.incremental' to see the exact firmware build
    Affected if Device is Huawei P8 and firmware version is earlier than GRA-TL00C01B366 (all versions are affected before this fix)

You are affected if you use a Huawei Mate 8, Mate S, or P8 device running firmware versions earlier than the fixed releases (NXT-AL10C00B386 for Mate 8, CRR-CL00C92B368 for Mate S, GRA-TL00C01B366 for P8).

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

Update affected devices to the specified software versions (NXT-AL10C00B386 or later for Mate 8, CRR-CL00C92B368 or later for Mate S, GRA-TL00C01B366 or later for P8) to receive the security patch.

Fix this in Mate S 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-2016-8792 — 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-2016-8792 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