Google Android Linux Kernel HTT_T2H_MSG_TYPE_MGMT_TX_COMPL_IND Message memory corruption

Summaryinfo

A vulnerability marked as critical has been reported in Google Android. The impacted element is an unknown function of the component Linux Kernel. This manipulation as part of HTT_T2H_MSG_TYPE_MGMT_TX_COMPL_IND Message causes memory corruption. This vulnerability appears as CVE-2018-5830. The attack requires local access. There is no available exploit. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability has been found in Google Android (Smartphone Operating System) (the affected version is unknown) and classified as critical. Affected by this vulnerability is an unknown code of the component Linux Kernel. The manipulation as part of a HTT_T2H_MSG_TYPE_MGMT_TX_COMPL_IND Message 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 processing the HTT_T2H_MSG_TYPE_MGMT_TX_COMPL_IND message, a buffer overflow can potentially occur 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 07/02/2018. The weakness was presented 07/06/2018 (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2018-5830 since 01/19/2018. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. 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.

See VDB-120503, VDB-120504, VDB-120515 and VDB-120522 for similar entries. 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