CVE-2021-0433: High severity Google Android vulnerability

Published Apr 1, 2021
·
Updated

In onCreate of DeviceChooserActivity.java, there is a possible way to bypass user consent when pairing a Bluetooth device due to a tapjacking/overlay attack. This could lead to local escalation of privilege and pairing malicious devices with no additional execution privileges needed. User interaction is needed for exploitation.

Affected Software

9 affected componentsFixes available
Google Android=8.1
Google Android=9.0
Google Android=10.0
Google Android=11.0
Google Android
android/platform/frameworks/base>=8.1:0<8.1:2021-04-01
8.1:2021-04-01
android/platform/frameworks/base>=9:0<9:2021-04-01
9:2021-04-01
android/platform/frameworks/base>=10:0<10:2021-04-01
10:2021-04-01
android/platform/frameworks/base>=11:0<11:2021-04-01
11:2021-04-01

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 8.1:2021-04-01
  2. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 9:2021-04-01
  3. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 10:2021-04-01
  4. Upgrade

    Upgrade android/platform/frameworks/base to a version that resolves this vulnerability.

    Fixed in 11:2021-04-01

Event History

Apr 1, 2021
Advisory Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionAffected Software
Apr 5, 2021
CVE Published
via Android·12:00 AM
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Apr 13, 2021
CVE Published
via MITRE·06:18 PM
Data Sourced
via MITRE·06:18 PM
DescriptionWeakness
Apr 20, 2022
Exploit Published
via GitHub·12:03 PM

Frequently Asked Questions

1

Which Android releases are affected?

The affected releases listed are Android 8.1, Android 9, Android 10, and Android 11.

2

What must an attacker do to exploit this issue?

The attacker needs to use a tapjacking or overlay attack against the device-pairing consent flow. User interaction is required, but no additional execution privileges are needed.

3

What is the impact if exploitation succeeds?

An attacker can bypass user consent for Bluetooth pairing and pair malicious Bluetooth devices. This can result in local escalation of privilege.

4

Is a fix available?

Yes. A patch is available; the issue is tracked as Android ID A-171221090 and is covered by the April 2021 Android security bulletin.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203