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 |
|---|---|---|
| 7.0 | $25k-$100k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Android 6.0/6.0.1/7.0/7.1.1. Affected by this issue is some unknown functionality of the component Mediaserver. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2017-0406. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as critical has been found in Google Android 6.0/6.0.1/7.0/7.1.1 (Smartphone Operating System). This affects some unknown processing of the component Mediaserver. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on 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. This affects the libhevc library. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-32915871.
The bug was discovered 02/06/2017. The weakness was shared 02/08/2017 with Alibaba (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2017-0406 since 11/29/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 11/12/2022). 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 2 days. During that time the estimated underground price was around $25k-$100k.
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 vulnerability database at SecurityFocus (BID 96046†). The entries VDB-96659, VDB-96660, VDB-96661 and VDB-96662 are related to this item. 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: 7.0VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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 🔍02/06/2017 🔍
02/06/2017 🔍
02/08/2017 🔍
02/08/2017 🔍
02/08/2017 🔍
11/12/2022 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Organization: Alibaba
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0406 (🔍)
GCVE (CVE): GCVE-0-2017-0406
GCVE (VulDB): GCVE-100-96669
SecurityFocus: 96046 - Google Android Mediaserver Multiple Remote Code Execution Vulnerabilities
OSVDB: - CVE-2017-0406 - Google - Android - High
SecurityTracker: 1037798
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 02/08/2017 21:07Updated: 11/12/2022 08:30
Changes: 02/08/2017 21:07 (65), 08/13/2020 21:39 (2), 11/12/2022 08:30 (2)
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.