| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android up to 8.0. This affects an unknown function of the component libminikin. The manipulation leads to access control. This vulnerability is documented as CVE-2017-0870. The attack needs to be performed locally. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, has been found in Google Android up to 8.0 (Smartphone Operating System). This issue affects an unknown code of the component libminikin. 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 summary by CVE is:
An elevation of privilege vulnerability in the Android framework (libminikin). Product: Android. Versions: 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID A-62134807.
The bug was discovered 12/04/2017. The weakness was released 12/06/2017 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2017-0870 since 11/29/2016. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful 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.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 102131†). Entries connected to this vulnerability are available at VDB-104864, VDB-107387, VDB-110232 and VDB-110233. 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: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2016 🔍12/01/2017 🔍
12/04/2017 🔍
12/06/2017 🔍
12/06/2017 🔍
12/06/2017 🔍
12/12/2019 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0870 (🔍)
GCVE (CVE): GCVE-0-2017-0870
GCVE (VulDB): GCVE-100-110261
SecurityFocus: 102131 - Google Android Framework Multiple Privilege Escalation Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 12/06/2017 22:07Updated: 12/12/2019 10:43
Changes: 12/06/2017 22:07 (62), 12/12/2019 10:43 (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.