CVE-2016-6180

UnknownEPSS 0.23%

Last modified

CVE-2016-6180 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.23% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.23%

13.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
HuaweiHonor 4c Firmwarechm-tl00c01_b535
HuaweiHonor 4c Firmwarechm-tl00c01b556
HuaweiHonor 4c Firmwarechm-tl00hc00_b535
HuaweiHonor 4c Firmwarechm-tl00hc00b556
HuaweiHonor 4c Firmwarechm-ul00c00b535
HuaweiHonor 4c Firmwarechm-ul00c00b556

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-6180?
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.
How severe is CVE-2016-6180?
Severity scoring for CVE-2016-6180 is pending analysis. The EPSS model estimates a 0.23% probability of exploitation in the next 30 days.
How do I fix CVE-2016-6180?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-6180?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST