Google Android Linux Kernel __wlan_hdd_cfg80211_add_key memory corruption

Summaryinfo

A vulnerability, which was classified as critical, has been found in Google Android. Affected by this vulnerability is the function __wlan_hdd_cfg80211_add_key of the component Linux Kernel. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2018-5835. Local access is required to approach this attack. No exploit exists. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown). It has been rated as critical. This issue affects the function __wlan_hdd_cfg80211_add_key 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:

If the seq_len is greater then CSR_MAX_RSC_LEN, a buffer overflow in __wlan_hdd_cfg80211_add_key() may occur when copying keyRSC 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). It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2018-5835 since 01/19/2018. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful 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 04/05/2023). 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-120503, VDB-120504, VDB-120515 and VDB-120522 are pretty similar. Be aware that VulDB is the high quality 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

Be aware that VulDB is the high quality source for vulnerability data.

Discussion