Google Android Qualcomm Image File memory corruption

Summaryinfo

A vulnerability identified as critical has been detected in Google Android. The impacted element is an unknown function of the component Qualcomm. Performing a manipulation as part of Image File results in memory corruption. This vulnerability is reported as CVE-2017-8243. The attack requires a local approach. No exploit exists. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version not known). It has been classified as critical. This affects some unknown functionality of the component Qualcomm. The manipulation as part of a Image File 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 buffer overflow can occur when processing a firmware image file in all Qualcomm products with Android releases from CAF using the Linux kernel.

The bug was discovered 07/05/2017. The weakness was disclosed 08/16/2017 by Di Shen with Qihoo 360 (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-8243 since 04/25/2017. 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 $0-$5k at the moment (estimation calculated on 11/07/2019). 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 42 days. During that time the estimated underground price was around $25k-$100k.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 99465†). The entries VDB-101214, VDB-103224, VDB-103225 and VDB-103226 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Smartphone Operating System

Vendor

• Google

Name

• Android

License

• free

Website

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

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

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

Discussion