Google Android prior 2016-07-05 on Nexus 5/5X/6/6P/7 2013 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 problematic has been discovered in Google Android on Nexus 5/5X/6/6P/7 2013. The impacted element is an unknown function of the component Qualcomm Performance. Such manipulation leads to access control. This vulnerability is traded as CVE-2016-3768. An attack has to be approached locally. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Google Android on Nexus 5/5X/6/6P/7 2013 (Smartphone Operating System). It has been rated as critical. Affected by this issue is an unknown functionality of the component Qualcomm Performance. 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. CVE summarizes:
The Qualcomm performance component in Android before 2016-07-05 on Nexus 5, 6, 5X, 6P, and 7 (2013) devices allows attackers to gain privileges via a crafted application, aka Android internal bug 28172137 and Qualcomm internal bug CR1010644.
The weakness was shared 07/06/2016 as Android Security Bulletin - July 2016 as confirmed security bulletin (Website). The advisory is shared for download at source.android.com. This vulnerability is handled as CVE-2016-3768 since 03/30/2016. The exploitation is known to be easy. The attack needs to be approached locally. The successful exploitation needs a simple authentication. 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 02/22/2019). 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.
Upgrading to version 2016-07-05 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The entries VDB-88897, VDB-88898, VDB-88899 and VDB-88900 are related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
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 2016-07-05
Timeline
03/30/2016 🔍07/06/2016 🔍
07/06/2016 🔍
07/10/2016 🔍
07/11/2016 🔍
02/22/2019 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - July 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3768 (🔍)
GCVE (CVE): GCVE-0-2016-3768
GCVE (VulDB): GCVE-100-88964
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 07/11/2016 11:05Updated: 02/22/2019 08:47
Changes: 07/11/2016 11:05 (55), 02/22/2019 08:47 (10)
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.