Google Android Linux Kernel length Kernel Memory memory corruption

Summaryinfo

A vulnerability has been found in Google Android and classified as critical. This affects an unknown part of the component Linux Kernel. Performing a manipulation of the argument length results in memory corruption (Kernel Memory). This vulnerability is identified as CVE-2017-14896. The attack is only possible with local access. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (the affected version unknown). It has been classified as critical. This affects an unknown part of the component Linux Kernel. The manipulation of the argument length with an unknown input leads to a memory corruption vulnerability (Kernel Memory). 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:

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, there is a memory allocation without a length field validation in the mobicore driver which can result in an undersize buffer allocation. Ultimately this can result in a kernel memory overwrite.

The bug was discovered 12/05/2017. The weakness was released 12/05/2017 (Website). It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2017-14896 since 09/28/2017. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/21/2019). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem.

Entries connected to this vulnerability are available at VDB-101212, VDB-102646, VDB-110201 and VDB-110202. 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