Vulnerabilities / Threats
8/6/2013
10:58 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Android Trojan Banking App Targets Master Key Vulnerability

Sluggish Android updates put users at risk. Could rising public awareness of the flaw lead carriers and device makers to patch more quickly?

9 Android Apps To Improve Security, Privacy
9 Android Apps To Improve Security, Privacy
(click image for larger view)
Security researchers have spotted a legitimate banking app for Android smartphones and tablets that has been "trojanized" using the so-called master key vulnerability. That flaw, which affects all versions of Android prior to version 4.2.2, can be used by attackers to inject malicious code into a digitally signed, legitimate Android app.

In this case, attackers have been offering a trojanized update for a legitimate online banking app distributed by South Korea's NH Nonghyup Bank. The Android app is used by up to 10 million people.

Running the malicious app triggers a screen asking users to enter their account details. "Should the user comply, their information would be sent to a remote malicious server controlled by the cybercriminal," said Peter Yan, a Trend Micro mobile security engineer, in a blog post. In other words, people who fall for the attack would be likely targets for cybercriminals trying to drain their bank accounts.

The trojanized banking app "shows just how dangerous the abuse of the master key vulnerability is to Android users," Yan said. "Furthermore, since it involves [tampering with] an app that is already in the device, the effect might not be at all noticeable to the user, until it is too late."

[ Want more Android vulnerability news? Read Android One-Click Google Apps Access Cracked. ]

The trojanized banking app isn't the first known attempt to exploit the master key vulnerability for malicious purposes. That accolade goes to a legitimate app used for making a doctor's appointments in China, for which Symantec reported finding trojanized versions two weeks ago. In that case, the attacker behind the revamped app had added code that allowed the device to be remotely controlled, and which could siphon the phone's international mobile equipment identity (IMEI) number and phone numbers stored on the device, as well as dial premium-rate numbers, thus draining the smartphone user's account and enriching attackers.

What both of those malicious apps have in common, besides abusing the same master-key vulnerability, is that they're only available from third-party app stores. That's a reminder to all Android users to download and install apps only from reputable sources. That means using the likes of Google Play or the Amazon Appstore for Android, or else an in-house, pre-vetted enterprise app store.

Unfortunately, few devices currently run Android 4.2.2, which is patched against the vulnerability. But Google has partially mitigated the flaw in older devices via its Verify Apps feature, which warns users when they try to install an app that's been flagged as malicious. While the feature was originally released for Android 4.2, it's since been automatically distributed to every device that runs Android version 2.3 and newer -- encompassing 95% of all Android devices -- that's configured to use Google Play.

While those are welcome protections, consumers in some countries -- such as China -- are blocked from accessing Google Play altogether, and must rely on third-party app stores. Their only recourse is to run mobile antivirus software, which will help detect and remove malware that attempts to abuse the master-key vulnerability.

What would automatically mitigate the vulnerability for a large swath of users, however, is if all handset manufacturers and carriers pushed timely Android updates or security patches for their devices. To date, of course, updates from some carriers and manufacturers have been patchy, sometimes taking months -- if ever -- to appear.

For example, Blue Box CTO Jeff Forristal discovered the vulnerability in February and privately reported it to Google, which quickly patched the bug in the Android Open Source Project and alerted business partners in March. More than four months later, however, only a handful of devices -- Samsung Galaxy S4 and HTC One devices running Android 4.2.2 or above -- have received a patch. That's the case even after other security researchers last month managed to identify the vulnerability, based on a non-technical preview of Forristal's Black Hat presentation, which he delivered Thursday.

If a full-on fix is still outstanding for most Android devices, Forristal said that the vulnerability had at least raised users' awareness of the glacial pace with which many carriers and handset manufacturers release Android updates. "Regardless of whether or not you feel users were truly at risk, [it] got users' attention, it got users asking the right questions," said Forristal last week in a Black Hat press conference. "I get inquiries from end users saying, who can I contact to ask for a device update? To me, that's a great education win ... and a great first step in helping to address what has largely been identified as a fracture in security in the Android device ecosystem."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mathew
50%
50%
Mathew,
User Rank: Apprentice
8/8/2013 | 11:57:40 AM
re: Android Trojan Banking App Targets Master Key Vulnerability
Very interesting question. Does the average consumer select between Android/iOS/Windows Phone/BlackBerry based on security, though? Because Android is still a runaway success.
Mathew
50%
50%
Mathew,
User Rank: Apprentice
8/8/2013 | 11:56:11 AM
re: Android Trojan Banking App Targets Master Key Vulnerability
Thanks very much, and in terms of "next steps," what would you recommend? Contacting the customer service center for your handset manufacturer or carrier? Logging a trouble ticket? Given all of the different carriers and manufacturers out there, I'm not sure there's a one-size-fits-all approach.
Jonathan_Camhi
50%
50%
Jonathan_Camhi,
User Rank: Apprentice
8/7/2013 | 8:58:36 PM
re: Android Trojan Banking App Targets Master Key Vulnerability
I wonder if the better security of iOS will wind up being a competitive advantage in the future as more malware makes its way into the Android ecosystem.
PES35A
50%
50%
PES35A,
User Rank: Apprentice
8/7/2013 | 2:19:49 PM
re: Android Trojan Banking App Targets Master Key Vulnerability
Mathew you have a great call to order, but you neglected to give consumers the "best" name, email address or mailing address to send letters to their carrier urging them to get the new updates tested and out to the devices.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web