| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android on Nexus. This vulnerability affects unknown code of the component Qualcomm Bootloader. The manipulation leads to access control. This vulnerability is listed as CVE-2016-3850. The attack must be carried out locally. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Google Android on Nexus (Smartphone Operating System) (affected version not known). This issue affects some unknown functionality of the component Qualcomm Bootloader. 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 weakness was presented 08/01/2016 as Android Security Bulletin - August 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-3850 since 03/30/2016. The exploitation is known to be easy. An attack has to be approached locally. A simple authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/12/2022). 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.
Upgrading 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 SecurityFocus (BID 92236†). See VDB-90455, VDB-90456, VDB-90457 and VDB-90458 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.3
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: Partially
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: 🔍
Patch: source.codeaurora.org
Timeline
03/30/2016 🔍08/01/2016 🔍
08/01/2016 🔍
08/01/2016 🔍
08/05/2016 🔍
08/06/2016 🔍
09/12/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - August 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3850 (🔍)
GCVE (CVE): GCVE-0-2016-3850
GCVE (VulDB): GCVE-100-90533
SecurityFocus: 92236 - Google Nexus Qualcomm Bootloader CVE-2016-3850 Privilege Escalation Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/06/2016 14:02Updated: 09/12/2022 10:25
Changes: 08/06/2016 14:02 (55), 03/20/2019 15:37 (13), 09/12/2022 10:25 (4)
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.