| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Google Android up to 4.x/5.x and classified as problematic. Impacted is an unknown function of the component Qualcomm RF. The manipulation leads to access control. This vulnerability is documented as CVE-2016-0844. The attack needs to be performed locally. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Google Android up to 4.x/5.x (Smartphone Operating System) and classified as critical. This issue affects an unknown part of the component Qualcomm RF. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Qualcomm RF driver in Android 6.x before 2016-04-01 does not properly restrict access to socket ioctl calls, which allows attackers to gain privileges via a crafted application, aka internal bug 26324307.
The weakness was released 04/04/2016 as ANDROID-26324307 as confirmed security bulletin (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-0844 since 12/16/2015. An attack has to be approached locally. A simple authentication is necessary for exploitation. 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 02/03/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 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-57905†). Entries connected to this vulnerability are available at VDB-81567, VDB-81568, VDB-81569 and VDB-81570. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 8.4VulDB Meta Temp Score: 8.2
VulDB Base Score: 8.4
VulDB Temp Score: 8.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.4
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: No
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 6.0/6.0.1
Timeline
12/16/2015 🔍12/25/2015 🔍
04/02/2016 🔍
04/04/2016 🔍
04/04/2016 🔍
04/05/2016 🔍
04/05/2016 🔍
04/17/2016 🔍
02/03/2019 🔍
Sources
Vendor: google.comAdvisory: ANDROID-26324307
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-0844 (🔍)
GCVE (CVE): GCVE-0-2016-0844
GCVE (VulDB): GCVE-100-81581
Vulnerability Center: 57905 - Google Android 6.0 and 6.0.1 before 2016-04-02 Local Code Execution due to a Vulnerability in Qualcomm RF Component, High
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 04/05/2016 09:13Updated: 02/03/2019 10:43
Changes: 04/05/2016 09:13 (64), 02/03/2019 10:43 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.