| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android. The affected element is an unknown function of the component Binder. Performing a manipulation results in access control. This vulnerability was named CVE-2016-8468. The attack needs to be approached locally. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Google Android (Smartphone Operating System) (affected version not known). This affects some unknown functionality of the component Binder. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability.
The bug was discovered 01/03/2017. The weakness was presented 01/05/2017 as Android Security Bulletin - January 2017 as confirmed advisory (Website). The advisory is shared at source.android.com. The public release was coordinated in cooperation with Google. This vulnerability is uniquely identified as CVE-2016-8468 since 10/05/2016. An attack has to be approached locally. A authentication is required for exploitation. Neither technical details nor an exploit are publicly available. 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 2 days. During that time the estimated underground price was around $25k-$100k.
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 95285†). See VDB-90138, VDB-94929, VDB-94930 and VDB-94931 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: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
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: 🔍
Timeline
10/05/2016 🔍01/03/2017 🔍
01/03/2017 🔍
01/04/2017 🔍
01/05/2017 🔍
01/05/2017 🔍
01/12/2017 🔍
10/27/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - January 2017
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2016-8468 (🔍)
GCVE (CVE): GCVE-0-2016-8468
GCVE (VulDB): GCVE-100-95013
SecurityFocus: 95285 - Google Pixel Binder CVE-2016-8468 Privilege Escalation Vulnerability
OSVDB: - CVE-2016-8468 - Linux - Kernel - Privilege Escalation Issue
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/04/2017 18:43Updated: 10/27/2022 14:28
Changes: 01/04/2017 18:43 (71), 10/27/2022 14:28 (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.