Actively exploited vulnerability
Android Kernel: memory corruption flaw under attack
CVE-2020-0041 · Android Kernel Out-of-Bounds Write Vulnerability
What is affected
Android Kernel is found on ordinary personal computers and phones, so this is not only a problem for companies. If you use it and have not updated since the fix was released, you are exposed.
Android Kernel binder_transaction of binder.c contains an out-of-bounds write vulnerability due to an incorrect bounds check that could allow for local privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0069 under exploit chain "AbstractEmu."
What an attacker can do
This is a memory corruption flaw. It lets an attacker corrupt the program's memory by feeding it specially crafted content: a web page, a file or a network message. The result ranges from a crash to the attacker running their own code.
- How it is reached
- Needs access to the device or a file opened on it
- Access the attacker needs
- A basic user account
- Does the victim have to do something?
- No, works without the victim doing anything
What to do
- Update Android Kernel now. Open the update or "About" screen, install whatever is offered and restart the app or device, because the fix is not active until you do.
- Turn on automatic updates so the next fix arrives without you having to look for it.
- If your device is too old to receive this update, stop using the affected app for anything sensitive and plan a replacement.
Apply updates per vendor instructions.
How urgent is it
CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on November 3, 2021, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by May 3, 2022, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.
The EPSS model estimates a 3.1% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 88% of all scored vulnerabilities.
Its CVSS severity score is 7.8 out of 10 (high), as recorded in the US National Vulnerability Database.
Technical description
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