CVE-2016-6184
HighSummary
The Camera driver in Huawei Honor 4C smartphones with software before version 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.
Risk Assessment
This vulnerability may lead to significant disruptions in device operation and potential unauthorized access to the system, posing a threat to user data security.
Recommendation
It is recommended to update the software to the latest version to mitigate this vulnerability and to monitor applications installed on devices.
Other vulnerabilities in Sterownik kamery w smartfonach Huawei Honor 4C
See all- CVE-2016-6183High
The Camera driver in Huawei Honor 4C smartphones with software before versions CHM-UL00C00B564, CHM-TL00C01B564, and CHM-TL00HC00B564 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application.
- CVE-2016-6182High
The Camera driver in Huawei Honor 4C smartphones with software before versions CHM-UL00C00B564, CHM-TL00C01B564, and CHM-TL00HC00B564 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application.
- CVE-2016-6181High
The Camera driver in Huawei Honor 4C smartphones with specific software versions allows attackers to cause a system crash or gain privileges via a crafted application.
- CVE-2016-6180High
The Camera driver in Huawei Honor 4C smartphones with software before versions CHM-UL00C00B564, CHM-TL00C01B564, and CHM-TL00HC00B564 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application.
Original NVD description (English source)
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-6180, CVE-2016-6181, CVE-2016-6182, and CVE-2016-6183.