Google Android Kernel Image memory corruption

Summaryinfo

A vulnerability identified as critical has been detected in Google Android. Affected by this vulnerability is an unknown functionality of the component Kernel Image Handler. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2018-5889. The attack must be initiated from a local position. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (affected version not known). This affects some unknown functionality of the component Kernel Image Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. 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:

While processing a compressed kernel image, a buffer overflow can 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 06/05/2018. The weakness was shared 07/06/2018 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2018-5889 since 01/19/2018. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price 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-120500, VDB-120498, VDB-120499 and VDB-120502 are related to this item. 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