Google Android up to 4.4.3/5.0.1/5.1.0 Qualcomm Performance access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $5k-$25k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Google Android up to 4.4.3/5.0.1/5.1.0. This affects an unknown part of the component Qualcomm Performance. Executing a manipulation can lead to access control. This vulnerability is tracked as CVE-2016-0819. The attack is restricted to local execution. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Google Android up to 4.4.3/5.0.1/5.1.0 (Smartphone Operating System) and classified as critical. This vulnerability affects an unknown functionality of the component Qualcomm Performance. 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:
The Qualcomm performance component in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49H, and 6.x before 2016-03-01 allows attackers to gain privileges via a crafted application, aka internal bug 25364034.
The weakness was disclosed 03/07/2016 with Trend Micro as Nexus Security Bulletin, March 2016 as confirmed security bulletin (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2016-0819 since 12/15/2015. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/01/2018). It is expected to see the exploit prices for this product increasing in the near future.The MITRE ATT&CK project declares the attack technique as T1068.
The vulnerability was handled as a non-public zero-day exploit for at least 130 days. During that time the estimated underground price was around $25k-$100k.
Upgrading to version 4.4.4, 5.0.2, 5.1.1 or 6.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 84250†) and Vulnerability Center (SBV-57037†). The entries VDB-81288, VDB-81289, VDB-81290 and VDB-81291 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 1.0
- 1.1
- 1.5
- 1.6
- 2.0
- 2.0.1
- 2.1
- 2.2
- 2.2.1
- 2.2.2
- 2.2.3
- 2.3
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 3.0
- 3.1
- 3.2
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 4.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.1
- 4.1.1
- 4.1.2
- 4.2
- 4.2.1
- 4.2.2
- 4.3
- 4.3.1
- 4.4
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 5.0
- 5.0.1
- 5.1.0
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
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
Timeline
10/29/2015 🔍12/15/2015 🔍
03/06/2016 🔍
03/06/2016 🔍
03/07/2016 🔍
03/07/2016 🔍
03/07/2016 🔍
03/09/2016 🔍
03/12/2016 🔍
09/01/2018 🔍
Sources
Vendor: google.comAdvisory: Nexus Security Bulletin, March 2016
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-0819 (🔍)
GCVE (CVE): GCVE-0-2016-0819
GCVE (VulDB): GCVE-100-81292
SecurityFocus: 84250 - Google Android Qualcomm Performance CVE-2016-0819 Remote Privilege Escalation Vulnerability
Vulnerability Center: 57037 - Google Android before 5.1.1 LMY49H and 6.0 before 2016-03-01 Remote Code Execution in Qualcomm Performance Component - CVE-2016-0819, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/09/2016 11:32Updated: 09/01/2018 08:49
Changes: 03/09/2016 11:32 (68), 09/01/2018 08:49 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.