WebView Exploit Affects Most Android Phones
Critical bug affects devices running Jelly Bean (4.2) and earlier Android OSs, including fully updated versions of Google Glass, says Metasploit.
An exploit for a vulnerability that affects an estimated 70% of all Android devices has been added to the Metasploit open-source penetration testing framework.
The “single-click” Metasploit exploit targets a vulnerability in a WebView component that’s used by the native Android browser, although the component can also be used by other apps. Although the vulnerability has been present in some devices for nearly two years, it wasn’t publicly disclosed until 14 months ago.
“This vulnerability is kind of a huge deal,” said Tod Beardsley, the technical lead for the Metasploit Framework, in a blog post. “I’m hopeful that by publishing an E-Z-2-Use Metasploit module that exploits it, we can maybe push some vendors toward ensuring that single-click vulnerabilities like this don’t last for 93+ weeks in the wild.”
The underlying privilege-escalation flaw, which involves a Java reflection API vulnerability, exists in versions of WebView prior to 4.2, and results from that component – in some cases – allow untrusted JavaScript code to be executed. As a result, an attacker could exploit the flaw to execute arbitrary commands.
According to Google, at least 73% of in-use Android devices run version 4.1 or earlier of the mobile operating system.
The Metasploit module was created by Rapid7 developer Joe Vennix and Accuvant Labs security researcher Joshua Drake. Drake reported on Redditthat the vulnerability has been successfully exploited – via the built-in Android browser – on pre-4.2 devices, including Google Glass. “I can confirm it not only affects the stock browser but it affects Google Glass in its fully updated form (Android 4.0.4),” said Drake.
According to an attack-demonstration video published by Rapid7, the bug can be exploited by tricking a user into scanning a malicious QR code that includes the attack code, which then triggers the vulnerability in the Android browser and gives the attacker command-shell access to the device.
But the vulnerability can be exploited in other ways, too. “A secondary attack vector involves the WebViews embedded inside a large number of Android applications,” says an overview published by Rapid7. “Ad integrations are perhaps the worst offender here.” In particular, if an attacker could gain man-in-the-middle access to a vulnerable application’s HTML connection, or to the cross-site scripting code used by the application, then the attacker could inject the malicious JavaScript code and gain command-shell access to the device.
How can Android users protect themselves against the vulnerability? That’s an open question. “Who do you lean on to get this patched? The big box retailer who sold it to you? The manufacturer of the phone hardware? The cellphone service provider? Google?” said Rapid7’s Beardsley. “It may seem a little spurious, but it’s a question that’s going to be asked by journalists, wonks, and – hopefully – consumer protection groups in the coming weeks.”
The problem of device manufacturers that ship products with Android installed and then fail to update them in a timely manner led the American Civil Liberties Union to file a complaint with the Federal Trade Commission last year. The ACLU requested that the agency investigate the country’s four major wireless carriers for unfair business practices, on the grounds that they hold customers to long-term contracts, yet often fail to keep those customers’ devices secure.
Pending patches from handset manufacturers and carriers, what else could be done to arrest these types of vulnerabilities? Cutting down on the fragmentation of the Android ecosystem would be a good start.
On that front, a leaked memo that surfaced Sunday suggests that Google is aiming to prevent handset manufacturers from releasing devices that don’t sport the latest version of the Android operating system, Mobile Bloom Newsfirst reported.
Google’s carrot – and stick – for handset makers is that by using the latest version of Android, their devices will have access to Google Mobile Services (GMS), meaning the Google Services Framework and Google Play Store.
Or in the words of the memo: “Starting February 2014, Google will no longer approve GMS distribution on new Android products that ship older platform releases. Each platform release will have a ‘GMS approval window’ that typically closes nine months after the next Android platform release is publicly available. (In other words, we all have nine months to get new products on the latest platform after its public release.)”
That push for handset vendors to build the latest, or at least a very recent, version of Android into their devices would carry information security benefits, too, because newer versions of the operating system include patches for a number of well known vulnerabilities.
That said, Google still faces an uphill battle when it comes to getting device manufacturers to issue timely security updates – or in some cases, any patches at all – for devices they have already sold.
-
-
- Updated - - -
-
Don’t click random links
Don’t scan sketchy QR codes
Don’t use sketchy or public wireless
Until your phone is patched 
