CVE-2020-0138 Memory corruption in Android
An out-of-bounds write in Android's Bluetooth stack allows remote code execution, though it requires a non-default configuration where bluetoothtbd is used.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-0138?
CVE-2020-0138 is a critical memory corruption vulnerability in Google Android, published on 11 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In get_element_attr_rsp of btif_rc.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution if bluetoothtbd were used, which it isn't in typical Android platforms, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-142878416
Weakness: CWE-787
Which versions are affected by CVE-2020-0138?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2020-0138?
No fix has been published for CVE-2020-0138 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-0138 being exploited?
There is no known exploitation of CVE-2020-0138 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Google Android
Sources
Also known as GHSA-pq68-mg4h-3gxg.