dbcve.org
P8 FirmwareOperating system · Huawei

CVE-2015-8681

HIGH · 7.8 CVSS v3.0 Published 2016-04-07
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
The ovisp driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL00 before GRA-CL00C92B230, GRA-CL10 before GRA-CL10C92B230, GRA-UL00 before GRA-UL00C00B230, and GRA-UL10 before GRA-UL10C00B230, and Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application with the camera permission, aka an "interface access control vulnerability."

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 ovisp camera driver in Huawei P8 (GRA-TL00, GRA-CL00, GRA-CL10, GRA-UL00, GRA-UL10) and Mate S (CRR-TL00, CRR-UL00, CRR-CL00) smartphones contains an interface access control vulnerability. A malicious application holding camera permission can exploit this flaw to cause system crashes (denial of service) or escalate privileges beyond its intended sandbox.

MitigationApply vendor-supplied firmware updates (GRA-TL00C01B230, GRA-CL00C92B230, GRA-CL10C92B230, GRA-UL00C00B230, GRA-UL10C00B230 for P8; CRR-TL00C01B160SP01, CRR-UL00C00B160, CRR-CL00C92B161 for Mate S) to patch the vulnerable ovisp driver.

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
P8 FirmwareOperating system
Affected:= gra-cl00= gra-cl10= gra-tl00= gra-ul00= gra-ul10
Mate S FirmwareOperating system
Affected:= crr-cl00= crr-tl00= crr-ul00

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 number
    Check the device settings or use 'getprop ro.product.model' or 'getprop ro.product.device' command to retrieve the exact model identifier
    Affected if The model is not one of GRA-TL00, GRA-CL00, GRA-CL10, GRA-UL00, GRA-UL10 (P8) or CRR-TL00, CRR-UL00, CRR-CL00 (Mate S)
  2. Check P8 firmware version
    For P8 devices, use 'getprop ro.build.version.emui' or check Settings > About Phone > Version to retrieve the firmware build number
    Affected if The firmware is one of gra-cl00, gra-cl10, gra-tl00, gra-ul00, or gra-ul10 variants (indicating the affected builds)
  3. Check Mate S firmware version
    For Mate S devices, use 'getprop ro.build.version.emui' or check Settings > About Phone > Version to retrieve the firmware build number
    Affected if The firmware is one of crr-cl00, crr-tl00, or crr-ul00 variants (indicating the affected builds)
  4. Verify ovisp camera driver presence
    Check for the presence of the ovisp driver module by listing /system/lib/modules/ or using 'ls -la /dev/ovisp*' to enumerate camera driver device nodes
    Affected if The ovisp driver device nodes exist and are accessible, indicating the vulnerable driver component is loaded

A user is affected if they own a Huawei P8 or Mate S device matching one of the listed model/firmware variants (GRA-TL00, GRA-CL00, GRA-CL10, GRA-UL00, GRA-UL10 for P8 or CRR-TL00, CRR-UL00, CRR-CL00 for Mate S) and the ovisp camera driver is present on the device.

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 updates (GRA-TL00C01B230, GRA-CL00C92B230, GRA-CL10C92B230, GRA-UL00C00B230, GRA-UL10C00B230 for P8; CRR-TL00C01B160SP01, CRR-UL00C00B160, CRR-CL00C92B161 for Mate S) to patch the vulnerable ovisp driver.

Fix this in P8 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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