VDB-92349 · CVE-2016-3922 · BID 93315

Google Android prior 6.0/6.0.1/7.0 Telephony 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.5$5k-$25k0.00

Summaryinfo

A vulnerability was found in Google Android. It has been classified as problematic. This issue affects some unknown processing of the component Telephony. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2016-3922. The attack must be initiated from a local position. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in Google Android (Smartphone Operating System). This affects an unknown code block of the component Telephony. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

libril/RilSapSocket.cpp in Telephony in Android 6.x before 2016-10-01 and 7.0 before 2016-10-01 relies on variable-length arrays, which allows attackers to gain privileges via a crafted application, aka internal bug 30202619.

The weakness was shared 10/03/2016 by Daniel Micay as Android Security Bulletin - October 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2016-3922 since 03/30/2016. An attack has to be approached locally. The requirement for exploitation is a authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/01/2019). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.

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

Upgrading to version 6.0, 6.0.1 or 7.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93315†). The entries VDB-83735, VDB-90675, VDB-90618 and VDB-90676 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.6

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

NVD Base Score: 7.8
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: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Android 6.0/6.0.1/7.0

Timelineinfo

03/30/2016 🔍
07/17/2016 +109 days 🔍
10/03/2016 +78 days 🔍
10/03/2016 +0 days 🔍
10/03/2016 +0 days 🔍
10/05/2016 +2 days 🔍
10/10/2016 +5 days 🔍
05/01/2019 +933 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - October 2016
Researcher: Daniel Micay
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-3922 (🔍)
GCVE (CVE): GCVE-0-2016-3922
GCVE (VulDB): GCVE-100-92349
SecurityFocus: 93315 - Google Android CVE-2016-3922 Remote Privilege Escalation Vulnerability

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

Entryinfo

Created: 10/05/2016 10:44
Updated: 05/01/2019 15:31
Changes: 10/05/2016 10:44 (59), 05/01/2019 15:31 (14)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!