| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Google Android 6.0/6.0.1. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component WiFi. This manipulation causes access control. This vulnerability appears as CVE-2016-0809. The attacker needs to be present on the local network. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in Google Android 6.0/6.0.1 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is an unknown function of the component WiFi. 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.
The weakness was presented 02/01/2016 as Nexus Security Bulletin - February 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2016-0809 since 12/15/2015. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. 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 07/06/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 databases at SecurityFocus (BID 82325†) and Vulnerability Center (SBV-56324†). See VDB-80765, VDB-80766, VDB-80767 and VDB-80768 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
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.8VulDB Meta Temp Score: 8.6
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 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: 🔍
Timeline
12/15/2015 🔍01/31/2016 🔍
02/01/2016 🔍
02/01/2016 🔍
02/01/2016 🔍
02/02/2016 🔍
02/06/2016 🔍
07/06/2022 🔍
Sources
Vendor: google.comAdvisory: Nexus Security Bulletin - February 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-0809 (🔍)
GCVE (CVE): GCVE-0-2016-0809
GCVE (VulDB): GCVE-100-80773
SecurityFocus: 82325
Vulnerability Center: 56324 - Google Android Local Network Privilege Escalation via a Crafted Application due to a Wi-Fi Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 02/02/2016 16:37Updated: 07/06/2022 18:30
Changes: 02/02/2016 16:37 (60), 07/23/2018 07:37 (10), 07/06/2022 18:30 (3)
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.