Home / Security / [News] More than 95% of active Android Devices vulnerable to the software based on ClickJacking

[News] More than 95% of active Android Devices vulnerable to the software based on ClickJacking

More than 95% of active Android Devices vulnerable

Security researchers at Skycure are upping the ante on a vulnerability that it says now leaves 95.4 percent of Android devices vulnerable to an attack that hands over control of a phone or tablet to an attacker.

Clickjacking attacks where users are tricked into enabling Android accessibility features are possible on a majority of devices, enterprise mobile security firm Skycure warned on Tuesday.

The accessibility features offered by the Android operating system can be highly useful for people with impaired vision, hearing or motor skills. However, the Accessibility Service has also been abused by cybercriminals to steal sensitive information and install applications on devices.

Since the accessibility features are disabled by default, attackers need to find a way to convince victims to enable them in order for their malware to work. In many cases, they achieve this by displaying misleading pop-up messages that instruct users to manually enable Accessibility.

In March, researchers at Skycure demonstrated how attackers can enable accessibility features on Android devices by using clickjacking. Basically, attackers create a game that requires the user to click on certain points on the screen. While the user believes they are playing a game, they are actually navigating through Android’s options menu and enabling Accessibility.

Google is well aware of the threat posed by clickjacking attacks so it has added additional protections starting with Android 5.0 Lollipop. Specifically, the company ensured that system permission dialogs – such as the final confirmation “OK” button when activating Accessibility – cannot be covered by an overlay.

However, Skycure researchers discovered that this protection can be bypassed by making a hole in the overlay just on top of the OK button. In order to avoid raising suspicion, the hole does not include the “OK” text and instead it’s placed on top of a white portion of the button.

Below you can read the full version of the Skycure researchers article.


SkycureThis is a follow up to our blog post during RSA, where we explained how a hacker, by combining two features of Android, Accessibility Services and the ability to draw over other apps, may gain control of the mobile device, including acquiring elevated privileges and exposing the content of all apps on the device. With this exploit, a hacker could persistently monitor all of a victim’s activity, and read and possibly compose corporate emails and documents via the victim’s device. This also enables ransomware exploits, where a hacker may elevate their permissions to remotely encrypt or wipe the device, potentially forcing the victim to pay money to get access to their own device.

Recall from the last post (click here to read it) that Android created Accessibility Services to provide user interface enhancements to help users interact with their device. The ability to draw over apps allows graphical overlays to programs that may allow touches to enact on the program below it, even if the overlay is not transparent. Combining these two features, a malicious hacker can trick a user into granting virtually unlimited permissions to their malware.

Android adds protection

Recognizing this potential, starting with Lollipop (5.x), Google added additional protection to the final “OK” button that would grant these accessibility permissions. In other words, Android programmers wanted to make sure that if a user was going to turn on Accessibility Services, the OK button could not be covered by an overlay, and the user would be sure to know what they are allowing.

I was in a hotel when it occurred to me that although the hotel door mostly blocked my view of the hallway outside, there was a peephole that was not blocking the view. This was my epiphany that led me to think that if there were a hole in the overlay, the OK button could be “mostly covered” and still accept a touch in the potentially very small area that was not covered, thereby bypassing the new protection and still hiding the true intent from the user. Elisha Eshed, back in the Skycure office, was quick to jump on this and verify that this method works on Lollipop devices, extending the attack surface of Accessibility Clickjacking to ALMOST ALL (98.8% at the time of discovery, 95.4% at the time of this post) active Android devices.

We will be covering additional details in an upcoming webinar on this topic. Register to attend here.

Webinar Register

Video of example attack

In this short video of this exploit in practice, you can see that it only takes a small hole in the overlay to obscure the Accessibility Services screen and still bypass the current protection.

In the above video, we show an example of such an attack, using a simple game overlayed over the Accessibility Settings dialogs, tricking the user into clicking specific obscured areas:

  1. The user is taken to accessibility settings.
  2. The user is prompted to navigate to the properties of the service we’re trying to enable.
  3. The user is prompted to enable the selected service.
  4. To make the user unknowingly approve the service’s permissions: He is tricked into clicking “the eye”, which is in fact the unobscured left part of the “OK” (approval) button.


To fully protect your device, it is advised to use an updated version of Android, download only apps from trusted sources, such as the Google Play Store, and run an updated version of a Mobile Threat Defense solution.

Note that Marshmallow (6.x) takes an additional precaution against this type of attack by requiring the user to manually and specifically allow an app to create a system overlay by changing permissions in Settings -> Apps -> Draw over apps settings. So although Marshmallow may still be vulnerable, it is significantly more difficult to exploit.

Responsible disclosure

Skycure takes pride in abiding by vendor’s responsible disclosure policy. Per that policy, we notified Google of this issue in March 2016. Following our correspondence with the Google Android Security team, they have decided not to fix this issue and accept this risk as a consequence of its current design. Due to the importance and widespread prevalence of Android, and after coordination with Google’s security team, we decided to publish this blog post and inform users of this security issue.

We would like thank the Google Security team for their quick response and ongoing commitment to the security of their users.

Are your mobile devices impacted? Find out with a free assessment. Find Out

Check Also

Kaspersky Lab: Threat Predictions in 2018

Automotive. The growing risk of a vehicle’s systems being infiltrated or having its safety, privacy …