VDB-91435 · CVE-2016-3890 · BID 92851

Google Android prior 4.4.4/5.0.2/5.1.1/6.0/6.0.1 Java Debug Wire Protocol 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.
6.8$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Android. This vulnerability affects unknown code of the component Java Debug Wire Protocol. This manipulation causes access control. This vulnerability is registered as CVE-2016-3890. The attack needs to be launched locally. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Android (Smartphone Operating System) and classified as critical. Affected by this vulnerability is an unknown functionality of the component Java Debug Wire Protocol. 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 weakness was published 09/06/2016 with Google as Android Security Bulletin - September 2016 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2016-3890 since 03/30/2016. Attacking locally is a requirement. The successful exploitation needs a single authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/15/2022). 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.

Upgrading to version 4.4.4, 5.0.2, 5.1.1, 6.0 or 6.0.1 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 92851†). Similar entries are available at VDB-91415, VDB-91416, VDB-91417 and VDB-91418. Statistical analysis made it clear that VulDB provides the best quality for 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.0
VulDB Meta Temp Score: 6.8

VulDB Base Score: 7.0
VulDB Temp Score: 6.7
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: Upgrade
Status: 🔍

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

Upgrade: Android 4.4.4/5.0.2/5.1.1/6.0/6.0.1

Timelineinfo

03/30/2016 🔍
09/06/2016 +160 days 🔍
09/06/2016 +0 days 🔍
09/06/2016 +0 days 🔍
09/11/2016 +5 days 🔍
09/11/2016 +0 days 🔍
09/15/2022 +2195 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - September 2016
Organization: Google
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-3890 (🔍)
GCVE (CVE): GCVE-0-2016-3890
GCVE (VulDB): GCVE-100-91435
SecurityFocus: 92851 - Google Android Java Debug Wire Protocol CVE-2016-3890 Privilege Escalation Vulnerability
SecurityTracker: 1036763

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

Entryinfo

Created: 09/11/2016 12:29
Updated: 09/15/2022 14:08
Changes: 09/11/2016 12:29 (54), 04/14/2019 09:05 (13), 09/15/2022 14:08 (4)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!