VDB-97659 · CVE-2017-0474 · BID 96717

Google Android 7.0/7.1.1 Mediaserver 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 identified as very critical has been detected in Google Android 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-0474. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as very critical has been found in Google Android 7.0/7.1.1 (Smartphone Operating System). This affects some unknown functionality 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. Product: Android. Versions: 7.0, 7.1.1. Android ID: A-32589224.

The bug was discovered 03/06/2017. The weakness was shared 03/08/2017 with Trend Micro (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-0474 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. 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 04/29/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†). The entries VDB-94929, VDB-94930, VDB-94931 and VDB-94932 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for 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 🔍
03/06/2017 +97 days 🔍
03/06/2017 +0 days 🔍
03/07/2017 +1 days 🔍
03/08/2017 +1 days 🔍
03/08/2017 +0 days 🔍
04/29/2025 +2974 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Organization: Trend Micro
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-0474 (🔍)
GCVE (CVE): GCVE-0-2017-0474
GCVE (VulDB): GCVE-100-97659
SecurityFocus: 96717 - Google Android Mediaserver Multiple Remote Code Execution Vulnerabilities
OSVDB: - CVE-2017-0474 - Google - Android - High
SecurityTracker: 1037968

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

Entryinfo

Created: 03/08/2017 11:08
Updated: 04/29/2025 18:50
Changes: 03/08/2017 11:08 (61), 09/04/2020 21:30 (6), 04/29/2025 18:50 (16)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!