| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android. Affected by this vulnerability is an unknown functionality of the component MediaTek Component. The manipulation leads to access control. This vulnerability is referenced as CVE-2016-8446. The attack can only be performed from a local environment. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known). It has been rated as critical. This issue affects some unknown functionality of the component MediaTek Component. 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 bug was discovered 01/03/2017. The weakness was published 01/05/2017 as Android Security Bulletin - January 2017 as confirmed advisory (Website). The advisory is shared at source.android.com. The public release has been coordinated with Google. The identification of this vulnerability is CVE-2016-8446 since 10/05/2016. An attack has to be approached locally. A simple authentication is required for exploitation. 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 10/27/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.
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 95229†). Similar entries are available at VDB-90138, VDB-94929, VDB-94930 and VDB-94931. Several companies clearly confirm that VulDB is the primary source for best 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.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
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-8446 (🔍)
GCVE (CVE): GCVE-0-2016-8446
GCVE (VulDB): GCVE-100-94985
SecurityFocus: 95229 - Google Android MediaTek Components Multiple Privilege Escalation Vulnerabilities
OSVDB: - CVE-2016-8446 - Google - Android - High
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/04/2017 18:43Updated: 10/27/2022 12:00
Changes: 01/04/2017 18:43 (66), 07/14/2020 11:41 (6), 10/27/2022 12:00 (3)
Complete: 🔍
Cache ID: 216:A0A:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.