Google Android 6.0/6.0.1/7.0/7.1.1 Mediaserver Media File memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.7 | $25k-$100k | 0.00 |
A vulnerability was found in Google Android 6.0/6.0.1/7.0/7.1.1 (Smartphone Operating System). It has been rated as very critical. This issue affects an unknown code block of the component Mediaserver. The manipulation as part of a Media File leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A remote code execution vulnerability in libavc 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-33641588.
The bug was discovered 04/05/2017. The weakness was disclosed 04/07/2017 by Jianjun Dai with Trend Micro (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2017-0538 since 11/29/2016. The attack may be initiated remotely. No form of authentication is needed for a successful 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/27/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 entries 99378, 99379, 99380 and 99381 are pretty similar.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
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: 🔍
Local: No
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 🔍04/03/2017 🔍
04/05/2017 🔍
04/07/2017 🔍
04/07/2017 🔍
04/08/2017 🔍
11/27/2022 🔍
Sources
Vendor: google.comAdvisory: securityfocus.com⛔
Researcher: Jianjun Dai
Organization: Trend Micro
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0538 (🔍)
SecurityTracker: 1038201
SecurityFocus: 97330 - Google Android Mediaserver Multiple Memory Corruption Vulnerabilities
OSVDB: - CVE-2017-0538 - Google - Android - High
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 04/08/2017 09:37Updated: 11/27/2022 09:46
Changes: 04/08/2017 09:37 (68), 08/26/2020 17:21 (1), 11/27/2022 09:46 (3)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.