Google Android ION Subsystem information disclosure

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.
3.6$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Google Android. Impacted is an unknown function of the component ION Subsystem/Binder/USB Driver/Networking Subsystem. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2016-8405. Attacking locally is a requirement. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Google Android (Smartphone Operating System) (affected version not known). This affects some unknown functionality of the component ION Subsystem/Binder/USB Driver/Networking Subsystem. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

An information disclosure vulnerability in kernel components including the ION subsystem, Binder, USB driver and networking subsystem could enable a local malicious application to access data outside of its permission levels. This issue is rated as Moderate because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.10, Kernel-3.18. Android ID: A-31651010.

The bug was discovered 01/03/2017. The weakness was published 01/12/2017 with Trend Micro (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-8405 since 10/05/2016. An attack has to be approached locally. A authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 9 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 97357 (Debian DSA-3791-1 : linux - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 175973 (Debian Security Update for Linux (DSA 3791-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (97357) and SecurityFocus (BID 94686†). Similar entries are available at VDB-90448, VDB-90450, VDB-93850 and VDB-94694. 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: 3.7
VulDB Meta Temp Score: 3.7

VulDB Base Score: 2.8
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.7
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
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

Nessus ID: 97357
Nessus Name: Debian DSA-3791-1 : linux - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 703791
OpenVAS Name: Debian Security Advisory DSA 3791-1 (linux - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

10/05/2016 🔍
12/05/2016 +61 days 🔍
01/03/2017 +29 days 🔍
01/12/2017 +9 days 🔍
01/12/2017 +0 days 🔍
01/13/2017 +1 days 🔍
02/22/2017 +40 days 🔍
02/24/2017 +2 days 🔍
07/20/2020 +1242 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: securityfocus.com⛔
Organization: Trend Micro
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-8405 (🔍)
GCVE (CVE): GCVE-0-2016-8405
GCVE (VulDB): GCVE-100-95265

OVAL: 🔍

SecurityFocus: 94686 - Google Android Kernel Components Multiple Information Disclosure Vulnerabilites
OSVDB: - CVE-2016-8405 - Android and Linux - Information Disclosure Issue

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

Entryinfo

Created: 01/13/2017 08:11
Updated: 07/20/2020 18:11
Changes: 01/13/2017 08:11 (75), 07/20/2020 18:11 (9)
Complete: 🔍
Cache ID: 216:8C2:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!