Google Android 6.0/6.0.1/7.0/7.1.1 Mediaserver memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $25k-$100k | 0.00 |
Summary
A vulnerability, which was classified as very critical, has been found in Google Android 6.0/6.0.1/7.0/7.1.1. This issue affects some unknown processing of the component Mediaserver. This manipulation causes memory corruption. This vulnerability is handled as CVE-2017-0466. The attack can be initiated remotely. There is not any exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as very critical was found in Google Android 6.0/6.0.1/7.0/7.1.1 (Smartphone Operating System). Affected by this vulnerability is an unknown functionality of the component Mediaserver. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A remote code execution vulnerability in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-33139050.
The bug was discovered 03/06/2017. The weakness was released 03/08/2017 with Trend Micro (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2017-0466 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. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 03/20/2025). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $100k and more.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at SecurityFocus (BID 96717†) and SecurityTracker (ID 1037968†). Entries connected to this vulnerability are available at VDB-94929, VDB-94930, VDB-94931 and VDB-94932. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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.7VulDB Meta Temp Score: 8.7
VulDB Base Score: 9.6
VulDB Temp Score: 9.6
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: Memory corruptionCWE: CWE-119
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2016 🔍03/06/2017 🔍
03/06/2017 🔍
03/07/2017 🔍
03/08/2017 🔍
03/08/2017 🔍
03/20/2025 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Organization: Trend Micro
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0466 (🔍)
GCVE (CVE): GCVE-0-2017-0466
GCVE (VulDB): GCVE-100-97651
SecurityFocus: 96717 - Google Android Mediaserver Multiple Remote Code Execution Vulnerabilities
OSVDB: - CVE-2017-0466 - Google - Android - High
SecurityTracker: 1037968
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/08/2017 11:06 AMUpdated: 03/20/2025 05:08 PM
Changes: 03/08/2017 11:06 AM (61), 09/04/2020 08:36 PM (6), 03/20/2025 05:08 PM (16)
Complete: 🔍
Cache ID: 244:9B9:40
No comments yet. Languages: en.
Please log in to comment.