Google Android up to 5.1.1/6.0 Mediaserver memory corruption

Summaryinfo

A vulnerability was found in Google Android up to 5.1.1/6.0. It has been classified as very critical. This affects an unknown function of the component Mediaserver. This manipulation causes memory corruption. This vulnerability is handled as CVE-2015-8072. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as very critical was found in Google Android up to 5.1.1/6.0 (Smartphone Operating System). Affected by this vulnerability is an unknown code block of the component Mediaserver. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 23881715, a different vulnerability than CVE-2015-6608 and CVE-2015-8073.

The weakness was released 11/03/2015 as 23881715 as confirmed bug report (Website). The advisory is shared at groups.google.com. This vulnerability is known as CVE-2015-8072 since 11/02/2015. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/12/2018). It is expected to see the exploit prices for this product increasing in the near future.

We expect the 0-day to have been worth approximately $100k and more.

Upgrading to version 5.1.1 LMY48X or 6.0 2015-11-01 eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (107827) and Vulnerability Center (SBV-54387†). Entries connected to this vulnerability are available at VDB-79022 and VDB-79023. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Smartphone Operating System

Vendor

• Google

Name

• Android

Version

• 1.0
• 1.1
• 1.5
• 1.6
• 2.0
• 2.0.1
• 2.1
• 2.2
• 2.2.1
• 2.2.2
• 2.2.3
• 2.3
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.3.6
• 2.3.7
• 3.0
• 3.1
• 3.2
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 4.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.1
• 4.1.1
• 4.1.2
• 4.2
• 4.2.1
• 4.2.2
• 4.3
• 4.3.1
• 4.4
• 4.4.1
• 4.4.2
• 4.4.3
• 4.4.4
• 5.0
• 5.0.1
• 5.0.2
• 5.1
• 5.1.1
• 6.0

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

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

Discussion