Google Android 4.4.3/5.0.1/5.1.0 Debuggerd access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android 4.4.3/5.0.1/5.1.0. This affects an unknown function of the component Debuggerd. Performing a manipulation results in access control. This vulnerability is identified as CVE-2016-2430. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Google Android 4.4.3/5.0.1/5.1.0 (Smartphone Operating System). This affects an unknown functionality of the component Debuggerd. 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:
libbacktrace/Backtrace.cpp in debuggerd in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-05-01 allows attackers to gain privileges via an application containing a crafted symbol name, aka internal bug 27299236.
The weakness was released 05/02/2016 as Android Security Bulletin - May 2016 as confirmed advisory (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2016-2430 since 02/18/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 11/07/2018). 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.
Entries connected to this vulnerability are available at VDB-80659, VDB-80660, VDB-80661 and VDB-83098. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Android 4.4.4/5.0.2/5.1.1/6.0/6.0.1
Timeline
02/18/2016 🔍05/02/2016 🔍
05/02/2016 🔍
05/03/2016 🔍
05/09/2016 🔍
11/07/2018 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - May 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-2430 (🔍)
GCVE (CVE): GCVE-0-2016-2430
GCVE (VulDB): GCVE-100-83091
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/03/2016 10:57Updated: 11/07/2018 16:24
Changes: 05/03/2016 10:57 (63), 11/07/2018 16:24 (2)
Complete: 🔍
Cache ID: 216:8C9:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.