Google Android lim_send_sme_probe_req_ind Request memory corruption

Summaryinfo

A vulnerability has been found in Google Android and classified as critical. This affects the function lim_send_sme_probe_req_ind. This manipulation as part of Request causes memory corruption. This vulnerability is tracked as CVE-2018-3565. The attack is restricted to local execution. No exploit exists. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (the affected version unknown). Affected by this vulnerability is the function lim_send_sme_probe_req_ind. The manipulation as part of a Request 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. The summary by CVE is:

While sending a probe request indication in lim_send_sme_probe_req_ind() in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel, a buffer overflow can occur.

The bug was discovered 05/11/2018. The weakness was disclosed 06/06/2018 (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2018-3565 since 12/19/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/15/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 26 days. During that time the estimated underground price was around $25k-$100k.

Applying a patch is able to eliminate this problem.

The entries VDB-117573, VDB-117574, VDB-119006 and VDB-119016 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best 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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion