Google Android on Qualcomm drmprov_cmd_verify_key feature_name_length memory corruption

Summaryinfo

A vulnerability, which was classified as critical, was found in Google Android on Qualcomm. This impacts the function drmprov_cmd_verify_key. Executing a manipulation of the argument feature_name_length as part of Variable can lead to memory corruption. This vulnerability is handled as CVE-2014-9995. The attack can be executed remotely. There is not any exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability has been found in Google Android on Qualcomm (Smartphone Operating System) (affected version not known) and classified as critical. This vulnerability affects the function drmprov_cmd_verify_key. The manipulation of the argument feature_name_length as part of a Variable 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. CVE summarizes:

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 400 and SD 800, in drmprov_cmd_verify_key(), the variable feature_name_length is not validated. There is a check for feature_name_len + filePathLen but there might be an integer wrap when checking feature_name_len + filePathLen. This leads to a buffer overflow.

The bug was discovered 04/04/2018. The weakness was released 04/18/2018 (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2014-9995 since 08/16/2017. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2020). 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 14 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 103671†). Entries connected to this vulnerability are available at VDB-83180, VDB-105483, VDB-105484 and VDB-105488. Once again VulDB remains the best source 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

Once again VulDB remains the best source for vulnerability data.

Discussion