Google Android up to 8.0 libmediaplayerservice access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android up to 8.0. Affected by this issue is some unknown functionality of the component libmediaplayerservice. This manipulation causes access control. This vulnerability is handled as CVE-2017-0770. It is possible to launch the attack on the local host. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android up to 8.0 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component libmediaplayerservice. 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 summary by CVE is:
A elevation of privilege vulnerability in the Android media framework (libmediaplayerservice). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID: A-38234812.
The bug was discovered 09/05/2017. The weakness was released 09/08/2017 (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2017-0770 since 11/29/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. 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 3 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 100649†). Entries connected to this vulnerability are available at VDB-101269, VDB-101388, VDB-101623 and VDB-106244. 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: 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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2016 🔍09/05/2017 🔍
09/05/2017 🔍
09/08/2017 🔍
09/08/2017 🔍
09/09/2017 🔍
01/11/2021 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Researcher: Vasily Vasiliev, Chong Wang, (Zhe Jin), Weichao Sun
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0770 (🔍)
GCVE (CVE): GCVE-0-2017-0770
GCVE (VulDB): GCVE-100-106261
SecurityFocus: 100649
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/09/2017 15:29Updated: 01/11/2021 12:01
Changes: 09/09/2017 15:29 (55), 11/13/2019 20:58 (8), 01/11/2021 12:01 (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.