VDB-97627 · CVE-2016-8417 · BID 96832

Google Android Qualcomm Camera Driver access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.4$25k-$100k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been classified as critical. This affects an unknown part of the component Qualcomm Camera Driver. This manipulation causes access control. This vulnerability is tracked as CVE-2016-8417. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability has been found in Google Android (Smartphone Operating System) (unknown version) and classified as critical. Affected by this vulnerability is an unknown code block of the component Qualcomm Camera Driver. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An elevation of privilege vulnerability in the Qualcomm camera driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process and is mitigated by current platform configurations. Product: Android. Versions: Kernel-3.10, Kernel-3.18. Android ID: A-32342399. References: QC-CR#1088824.

The bug was discovered 01/03/2017. The weakness was disclosed 03/08/2017 with Baidu (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2016-8417 since 10/05/2016. Attacking locally is a requirement. The requirement for exploitation is a single authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 09/04/2020). It is expected to see the exploit prices for this product increasing in the near future.The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 63 days. During that time the estimated underground price was around $25k-$100k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 96832†). The entries VDB-94929, VDB-94930, VDB-94931 and VDB-94932 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.4

VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/05/2016 🔍
01/03/2017 +90 days 🔍
03/06/2017 +62 days 🔍
03/07/2017 +1 days 🔍
03/08/2017 +1 days 🔍
03/08/2017 +0 days 🔍
09/04/2020 +1276 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Organization: Baidu
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-8417 (🔍)
GCVE (CVE): GCVE-0-2016-8417
GCVE (VulDB): GCVE-100-97627
SecurityFocus: 96832 - Google Nexus Qualcomm Camera Driver CVE-2016-8417 Privilege Escalation Vulnerability
OSVDB: - CVE-2016-8417 - Linux - Kernel - Privilege Escalation Issue

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 03/08/2017 10:59
Updated: 09/04/2020 17:20
Changes: 03/08/2017 10:59 (60), 09/04/2020 17:20 (6)
Complete: 🔍
Cache ID: 216:CED:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!