VDB-99377 · CVE-2017-0538 · BID 97330

Google Android 6.0/6.0.1/7.0/7.1.1 Mediaserver Media File memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.7$25k-$100k0.00

Summaryinfo

A vulnerability was found in Google Android 6.0/6.0.1/7.0/7.1.1. It has been classified as very critical. This vulnerability affects unknown code of the component Mediaserver. The manipulation as part of Media File leads to memory corruption. This vulnerability is uniquely identified as CVE-2017-0538. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

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 vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97330†). The entries VDB-99378, VDB-99379, VDB-99380 and VDB-99381 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.7
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/29/2016 🔍
04/03/2017 +125 days 🔍
04/05/2017 +2 days 🔍
04/07/2017 +2 days 🔍
04/07/2017 +0 days 🔍
04/08/2017 +1 days 🔍
11/27/2022 +2059 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: securityfocus.com⛔
Researcher: Jianjun Dai
Organization: Trend Micro
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0538 (🔍)
GCVE (CVE): GCVE-0-2017-0538
GCVE (VulDB): GCVE-100-99377
SecurityFocus: 97330 - Google Android Mediaserver Multiple Memory Corruption Vulnerabilities
OSVDB: - CVE-2017-0538 - Google - Android - High
SecurityTracker: 1038201

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 04/08/2017 09:37
Updated: 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: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!