dbcve.org
Honor 4c FirmwareOperating system · Huawei

CVE-2016-6180

HIGH · 7.0 CVSS v3.0 Published 2016-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 Camera driver in Huawei Honor 4C smartphones with software CHM-UL00C00 before CHM-UL00C00B564, CHM-TL00C01 before CHM-TL00C01B564, and CHM-TL00C00 before CHM-TL00HC00B564 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application, a different vulnerability than CVE-2016-6181, CVE-2016-6182, CVE-2016-6183, and CVE-2016-6184.

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 vulnerability in the Camera driver of Huawei Honor 4C smartphones (CHM-UL00, CHM-TL00, CHM-TL00 variants) allows a malicious application to trigger either a system crash (denial of service) or escalate privileges. The flaw exists in the camera driver component and is exploitable through specially crafted application code.

MitigationApply vendor firmware updates (CHM-UL00C00B564, CHM-TL00C01B564, or CHM-TL00HC00B564 or later) to patched versions. Users should avoid installing applications from untrusted sources to reduce attack surface.

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
Honor 4c FirmwareOperating system
Affected:= chm-tl00c01_b535= chm-tl00c01b556= chm-tl00hc00_b535= chm-tl00hc00b556= chm-ul00c00b535= chm-ul00c00b556

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

CVSS:3.0/AV:L/AC:H/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
    Go to Settings > About Phone on the Huawei Honor 4C and verify the model number is one of: CHM-UL00, CHM-TL00, or CHM-TL00H (or variants like CHM-TL00C01, CHM-TL00HC00, CHM-UL00C00)
    Affected if Device model matches Honor 4C variants (CHM-UL00, CHM-TL00, CHM-TL00H)
  2. Check installed firmware version
    In Settings > About Phone > Version, locate the build number or firmware version. Compare it to the affected versions: chm-tl00c01_b535, chm-tl00c01b556, chm-tl00hc00_b535, chm-tl00hc00b556, chm-ul00c00b535, chm-ul00c00b556
    Affected if Firmware version exactly matches one of the six affected versions listed
  3. Verify camera driver is accessible
    Check if the camera application can be launched and accesses the camera driver. Use Android debugging (adb shell) to inspect /dev/video* or /sys/class/video4linux/ for camera device nodes, or attempt to access the camera via any application
    Affected if Camera driver device nodes exist and are accessible to applications (vulnerability requires camera driver to be present and exposed)
  4. Confirm patch level
    Look for the firmware version in Settings > About Phone. The patched versions are B564 or later (CHM-UL00C00B564, CHM-TL00C01B564, CHM-TL00HC00B564). If the version number is lower than B564, the device remains vulnerable
    Affected if Firmware version is below B564 (i.e., B535 or B556)

Device is affected if it is a Huawei Honor 4C (CHM-UL00, CHM-TL00, or CHM-TL00H variant) running firmware version B535 or B556 with an accessible camera driver component.

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 (CHM-UL00C00B564, CHM-TL00C01B564, or CHM-TL00HC00B564 or later) to patched versions. Users should avoid installing applications from untrusted sources to reduce attack surface.

Fix this in Honor 4c Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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