VAR-201609-0060
Vulnerability from variot - Updated: 2025-04-13 23:14The 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-6182, CVE-2016-6183, and CVE-2016-6184. This vulnerability CVE-2016-6180 , CVE-2016-6182 , CVE-2016-6183 ,and CVE-2016-6184 Is a different vulnerability. Supplementary information : CWE Vulnerability type by CWE-284: Improper Access Control ( Inappropriate access control ) Has been identified. http://cwe.mitre.org/data/definitions/284.htmlDenial of service operations through a specially crafted application by an attacker ( System crash ) It may be put into a state or it may be authorized. HuaweiHonor4C (Huawei Glory 4C) is a smartphone product from China's Huawei company. The HuaweiHonor4C driver has an input validation vulnerability. An attacker can induce a user to install a malicious application and use the vulnerability to pass specific parameters to the Camera driver, causing a system reboot or user privilege escalation. Huawei Honor 4C is prone to multiple unspecified security vulnerabilities Limited information is currently available regarding these issues. We will update this BID as more information emerges. The following versions are vulnerable: Huawei Honor 4C CHM-UL00C00B535 through CHM-UL00C00B556 Huawei Honor 4C CHM-TL00C01 B535 through CHM-TL00C01B556 Huawei Honor 4C CHM-TL00HC00 B535 through CHM-TL00HC00B556
Show details on source website{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-201609-0060",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-ul00c00b556"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-tl00c01_b535"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-tl00hc00_b535"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-tl00hc00b556"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-ul00c00b535"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 1.6,
"vendor": "huawei",
"version": "chm-tl00c01b556"
},
{
"model": "honor 4c \u003echm-ul00c00b535,\u003cchm-ul00c00b556",
"scope": null,
"trust": 1.2,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c \u003echm-tl00c01 b535,\u003cchm-tl00c01b556",
"scope": null,
"trust": 1.2,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c \u003echm-tl00hc00 b535,\u003cchm-tl00hc00b556",
"scope": null,
"trust": 1.2,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c",
"scope": "lt",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-ul00c00"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-tl00hc00b564"
},
{
"model": "honor 4c",
"scope": "lt",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-tl00c00"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-ul00c00b564"
},
{
"model": "honor 4c",
"scope": "lt",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-tl00c01"
},
{
"model": "honor 4c",
"scope": "eq",
"trust": 0.8,
"vendor": "huawei",
"version": "chm-tl00c01b564"
},
{
"model": "honor 4c",
"scope": null,
"trust": 0.8,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-ul00c00b556",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-ul00c00b535",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00hc00b556",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00hc00 b535",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00c01b556",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00c01 b535",
"scope": null,
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-ul00c00b564",
"scope": "ne",
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00hc00b564",
"scope": "ne",
"trust": 0.3,
"vendor": "huawei",
"version": null
},
{
"model": "honor 4c chm-tl00c01b564",
"scope": "ne",
"trust": 0.3,
"vendor": "huawei",
"version": null
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "BID",
"id": "91807"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/h:huawei:honor_4c",
"vulnerable": true
},
{
"cpe22Uri": "cpe:/o:huawei:honor_4c_firmware",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Yang Chengming, Yang Chao, You Ning, Xiao Peng and Song Yang of Alibaba Mobile Security Team.",
"sources": [
{
"db": "BID",
"id": "91807"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
}
],
"trust": 0.9
},
"cve": "CVE-2016-6181",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"accessComplexity": "MEDIUM",
"accessVector": "LOCAL",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "COMPLETE",
"baseScore": 6.9,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 3.4,
"id": "CVE-2016-6181",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "MEDIUM",
"trust": 1.8,
"vectorString": "AV:L/AC:M/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
{
"accessComplexity": "HIGH",
"accessVector": "LOCAL",
"authentication": "NONE",
"author": "CNVD",
"availabilityImpact": "COMPLETE",
"baseScore": 6.2,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 1.9,
"id": "CNVD-2016-05173",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "MEDIUM",
"trust": 0.6,
"vectorString": "AV:L/AC:H/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
{
"accessComplexity": "HIGH",
"accessVector": "LOCAL",
"authentication": "NONE",
"author": "CNVD",
"availabilityImpact": "COMPLETE",
"baseScore": 6.2,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 1.9,
"id": "CNVD-2016-05176",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "MEDIUM",
"trust": 0.6,
"vectorString": "AV:L/AC:H/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
{
"accessComplexity": "MEDIUM",
"accessVector": "LOCAL",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "COMPLETE",
"baseScore": 6.9,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 3.4,
"id": "VHN-95001",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "MEDIUM",
"trust": 0.1,
"vectorString": "AV:L/AC:M/AU:N/C:C/I:C/A:C",
"version": "2.0"
}
],
"cvssV3": [
{
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"author": "nvd@nist.gov",
"availabilityImpact": "HIGH",
"baseScore": 7.0,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"exploitabilityScore": 1.0,
"id": "CVE-2016-6181",
"impactScore": 5.9,
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"trust": 1.8,
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.0"
}
],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2016-6181",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "NVD",
"id": "CVE-2016-6181",
"trust": 0.8,
"value": "High"
},
{
"author": "CNVD",
"id": "CNVD-2016-05173",
"trust": 0.6,
"value": "MEDIUM"
},
{
"author": "CNVD",
"id": "CNVD-2016-05176",
"trust": 0.6,
"value": "MEDIUM"
},
{
"author": "CNNVD",
"id": "CNNVD-201607-499",
"trust": 0.6,
"value": "MEDIUM"
},
{
"author": "VULHUB",
"id": "VHN-95001",
"trust": 0.1,
"value": "MEDIUM"
}
]
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "VULHUB",
"id": "VHN-95001"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "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-6182, CVE-2016-6183, and CVE-2016-6184. This vulnerability CVE-2016-6180 , CVE-2016-6182 , CVE-2016-6183 ,and CVE-2016-6184 Is a different vulnerability. Supplementary information : CWE Vulnerability type by CWE-284: Improper Access Control ( Inappropriate access control ) Has been identified. http://cwe.mitre.org/data/definitions/284.htmlDenial of service operations through a specially crafted application by an attacker ( System crash ) It may be put into a state or it may be authorized. HuaweiHonor4C (Huawei Glory 4C) is a smartphone product from China\u0027s Huawei company. The HuaweiHonor4C driver has an input validation vulnerability. An attacker can induce a user to install a malicious application and use the vulnerability to pass specific parameters to the Camera driver, causing a system reboot or user privilege escalation. Huawei Honor 4C is prone to multiple unspecified security vulnerabilities\nLimited information is currently available regarding these issues. We will update this BID as more information emerges. \nThe following versions are vulnerable:\nHuawei Honor 4C CHM-UL00C00B535 through CHM-UL00C00B556\nHuawei Honor 4C CHM-TL00C01 B535 through CHM-TL00C01B556\nHuawei Honor 4C CHM-TL00HC00 B535 through CHM-TL00HC00B556",
"sources": [
{
"db": "NVD",
"id": "CVE-2016-6181"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "BID",
"id": "91807"
},
{
"db": "VULHUB",
"id": "VHN-95001"
}
],
"trust": 3.06
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2016-6181",
"trust": 3.4
},
{
"db": "BID",
"id": "91807",
"trust": 2.1
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556",
"trust": 0.8
},
{
"db": "CNVD",
"id": "CNVD-2016-05173",
"trust": 0.6
},
{
"db": "CNVD",
"id": "CNVD-2016-05176",
"trust": 0.6
},
{
"db": "NSFOCUS",
"id": "34733",
"trust": 0.6
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499",
"trust": 0.6
},
{
"db": "VULHUB",
"id": "VHN-95001",
"trust": 0.1
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "VULHUB",
"id": "VHN-95001"
},
{
"db": "BID",
"id": "91807"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"id": "VAR-201609-0060",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "VULHUB",
"id": "VHN-95001"
}
],
"trust": 2.17301588
},
"iot_taxonomy": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot_taxonomy#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"category": [
"Network device"
],
"sub_category": null,
"trust": 1.2
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
}
]
},
"last_update_date": "2025-04-13T23:14:14.450000Z",
"patch": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/patch#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"title": "huawei-sa-20160716-01-smartphone",
"trust": 0.8,
"url": "http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20160716-01-smartphone-en"
},
{
"title": "HuaweiHonor4C driver patch for input validation vulnerability",
"trust": 0.6,
"url": "https://www.cnvd.org.cn/patchInfo/show/79493"
},
{
"title": "HuaweiHonor4C driver input verification vulnerability (CNVD-2016-05176) patch",
"trust": 0.6,
"url": "https://www.cnvd.org.cn/patchInfo/show/79496"
},
{
"title": "Huawei Honor 4C Fixes for driver input verification security vulnerabilities",
"trust": 0.6,
"url": "http://www.cnnvd.org.cn/web/xxk/bdxqById.tag?id=62994"
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "CWE-284",
"trust": 1.1
},
{
"problemtype": "CWE-Other",
"trust": 0.8
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-95001"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 3.2,
"url": "http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20160716-01-smartphone-en"
},
{
"trust": 1.8,
"url": "http://www.securityfocus.com/bid/91807"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2016-6181"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2016-6181"
},
{
"trust": 0.6,
"url": "http://www.nsfocus.net/vulndb/34733"
},
{
"trust": 0.3,
"url": "http://www.huawei.com"
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "VULHUB",
"id": "VHN-95001"
},
{
"db": "BID",
"id": "91807"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"db": "VULHUB",
"id": "VHN-95001"
},
{
"db": "BID",
"id": "91807"
},
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2016-07-22T00:00:00",
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"date": "2016-07-22T00:00:00",
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"date": "2016-09-07T00:00:00",
"db": "VULHUB",
"id": "VHN-95001"
},
{
"date": "2016-07-16T00:00:00",
"db": "BID",
"id": "91807"
},
{
"date": "2016-09-09T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"date": "2016-07-19T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"date": "2016-09-07T19:28:05.830000",
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2016-07-22T00:00:00",
"db": "CNVD",
"id": "CNVD-2016-05173"
},
{
"date": "2016-07-22T00:00:00",
"db": "CNVD",
"id": "CNVD-2016-05176"
},
{
"date": "2016-09-08T00:00:00",
"db": "VULHUB",
"id": "VHN-95001"
},
{
"date": "2016-07-16T00:00:00",
"db": "BID",
"id": "91807"
},
{
"date": "2016-09-09T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2016-004556"
},
{
"date": "2016-09-08T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201607-499"
},
{
"date": "2025-04-12T10:46:40.837000",
"db": "NVD",
"id": "CVE-2016-6181"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "local",
"sources": [
{
"db": "BID",
"id": "91807"
},
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
}
],
"trust": 0.9
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Huawei Honor 4C Smartphone software Camera Service disruption in drivers (DoS) Vulnerabilities",
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2016-004556"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "input validation",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-201607-499"
}
],
"trust": 0.6
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.