Google Android up to 4.x/5.x Texas Instruments Haptic 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.7$5k-$25k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Google Android up to 4.x/5.x. Affected is an unknown function of the component Texas Instruments Haptic Driver. Executing a manipulation can lead to access control. This vulnerability is handled as CVE-2016-2409. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Google Android up to 4.x/5.x (Smartphone Operating System). This vulnerability affects an unknown functionality of the component Texas Instruments Haptic 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. CVE summarizes:

A Texas Instruments (TI) haptic kernel driver in Android 6.x before 2016-04-01 allows attackers to gain privileges via a crafted application that leverages control over a service that can call this driver, aka internal bug 25981545.

The weakness was released 04/04/2016 as ANDROID-25981545 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability was named CVE-2016-2409 since 02/18/2016. Local access is required to approach this attack. The successful exploitation needs a single authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 02/03/2019). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

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

Upgrading to version 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 Vulnerability Center (SBV-57919†). Entries connected to this vulnerability are available at VDB-81567, VDB-81568, VDB-81569 and VDB-81570. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.1
VulDB Meta Temp Score: 7.9

VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
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

Timelineinfo

12/25/2015 🔍
02/18/2016 +55 days 🔍
04/04/2016 +46 days 🔍
04/04/2016 +0 days 🔍
04/04/2016 +0 days 🔍
04/05/2016 +1 days 🔍
04/05/2016 +0 days 🔍
04/17/2016 +11 days 🔍
02/03/2019 +1022 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: ANDROID-25981545
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-2409 (🔍)
GCVE (CVE): GCVE-0-2016-2409
GCVE (VulDB): GCVE-100-81586
Vulnerability Center: 57919 - Google Android 6.0 and 6.0.1 before 2016-04-02 Remote Code Execution Vulnerability - CVE-2016-2409, High

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

Entryinfo

Created: 04/05/2016 09:13
Updated: 02/03/2019 10:46
Changes: 04/05/2016 09:13 (64), 02/03/2019 10:46 (10)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit 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!