Google Android binder.c binder_transaction out-of-bounds write

Summaryinfo

A vulnerability has been found in Google Android and classified as critical. The affected element is the function binder_transaction of the file binder.c. Performing a manipulation results in out-of-bounds write. This vulnerability is known as CVE-2020-0041. Attacking locally is a requirement. Furthermore, an exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as critical has been found in Google Android (Smartphone Operating System) (the affected version unknown). This affects the function binder_transaction of the file binder.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145988638References: Upstream kernel

The weakness was published 03/10/2020. This vulnerability is uniquely identified as CVE-2020-0041 since 10/17/2019. An attack has to be approached locally. A authentication is necessary for exploitation. Technical details and a exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/17/2025). It is expected to see the exploit prices for this product increasing in the near future.

It is declared as attacked. The vulnerability scanner Nessus provides a plugin with the ID 250170 (Linux Distros Unpatched Vulnerability : CVE-2020-0041), which helps to determine the existence of the flaw in a target environment. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 11/03/2021 with a due date of 05/03/2022:

Apply updates per vendor instructions.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at Tenable (250170). Similar entries are available at VDB-151249, VDB-151248, VDB-151247 and VDB-151246. 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