Google Android Linux Kernel dci_process_ctrl_status memory corruption

Summaryinfo

A vulnerability has been found in Google Android and classified as critical. This affects the function dci_process_ctrl_status of the component Linux Kernel. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2018-5897. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Android (Smartphone Operating System) (the affected version unknown). This issue affects the function dci_process_ctrl_status of the component Linux Kernel. 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. The summary by CVE is:

While reading the data from buffer in dci_process_ctrl_status() there can be buffer over-read problem if the len is not checked correctly in Android releases from CAF using the linux kernel (Android for MSM, Firefox OS for MSM, QRD Android) before security patch level 2018-06-05.

The bug was discovered 06/05/2018. The weakness was disclosed 07/06/2018 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2018-5897 since 01/19/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/26/2020). 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. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The entries VDB-120500, VDB-120498, VDB-120499 and VDB-120502 are pretty similar. 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

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