Google Android up to 4.4.3/5.0.1/5.1.0/6.x Mediaserver memory corruption

Summaryinfo

A vulnerability was found in Google Android up to 4.4.3/5.0.1/5.1.0/6.x. It has been declared as very critical. The impacted element is an unknown function of the component Mediaserver. Such manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2016-2463. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Google Android up to 4.4.3/5.0.1/5.1.0/6.x (Smartphone Operating System). Affected by this issue is some unknown processing of the component Mediaserver. 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. CVE summarizes:

Multiple integer overflows in the h264dec component in libstagefright in mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-06-01 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file that triggers a large memory allocation, aka internal bug 27855419.

The weakness was disclosed 06/13/2016 as 27855419 as confirmed advisory (Website). The advisory is available at android.googlesource.com. This vulnerability is handled as CVE-2016-2463 since 02/18/2016. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 01/18/2019). It is expected to see the exploit prices for this product increasing in the near future.

As 0-day the estimated underground price was around $100k and more.

Upgrading to version 4.4.4, 5.0.2, 5.1.1 or 6.0 2016-06-01 eliminates this vulnerability.

The entries VDB-87840, VDB-87841, VDB-87843 and VDB-87844 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit 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.1.0
• 6.x

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 best quality of vulnerability data, you may have to visit VulDB.

Discussion