CVE-2020-0041
Android Kernel Out-of-Bounds Write Vulnerability
Android Kernel
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
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 3 November 2021. US federal agencies were required to remediate it by 3 May 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 3.1%, which is higher than 87.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2020-0041 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2020-0041.
What does CVE-2020-0041 affect?
CVE-2020-0041 affects Android Kernel. 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
How severe is CVE-2020-0041?
CVE-2020-0041 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 3.1%, higher than 87.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 3 May 2022.
How should organisations respond to CVE-2020-0041?
Apply the vendor patch for Android Kernel as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.