VDB-97661 · CVE-2017-0476 · BID 96756

Google Android 6.0/6.0.1/7.0/7.1.1 AOSP Messaging 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.
7.0$25k-$100k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Android 6.0/6.0.1/7.0/7.1.1. This vulnerability affects unknown code of the component AOSP Messaging. The manipulation leads to memory corruption. This vulnerability is documented as CVE-2017-0476. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Android 6.0/6.0.1/7.0/7.1.1 (Smartphone Operating System). This issue affects an unknown code of the component AOSP Messaging. The manipulation with an unknown input 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 AOSP Messaging could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as High due to the possibility of remote code execution within the context of an unprivileged process. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-33388925.

The bug was discovered 03/06/2017. The weakness was released 03/08/2017 with Tencent (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2017-0476 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 05/14/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 $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 databases at SecurityFocus (BID 96756†) and SecurityTracker (ID 1037968†). Entries connected to this vulnerability are available at VDB-94929, VDB-94930, VDB-94931 and VDB-94932. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

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 🔍
05/14/2025 +2989 days 🔍

Sourcesinfo

Vendor: google.com

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

CVE: CVE-2017-0476 (🔍)
GCVE (CVE): GCVE-0-2017-0476
GCVE (VulDB): GCVE-100-97661
SecurityFocus: 96756 - Google Android AOSP Messaging CVE-2017-0476 Memory Corruption Vulnerability
OSVDB: - CVE-2017-0476 - Google - Android - Medium
SecurityTracker: 1037968

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

Entryinfo

Created: 03/08/2017 11:09
Updated: 05/14/2025 15:56
Changes: 03/08/2017 11:09 (55), 09/04/2020 21:47 (12), 05/14/2025 15:56 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!