Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Mobile

12/7/2017
01:00 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Man-in-the-Middle Flaw in Major Banking, VPN Apps Exposes Millions

New research from University of Birmingham emphasizes importance of securing high-risk mobile apps.

[This article was updated on 12/11 to clarify the Bank of America app cited by researchers was Bank of America Health]

Researchers from the UK have uncovered a serious vulnerability in the way nine banking and VPN apps handle encrypted communication that puts tens of millions of users at risk of man-in-the-middle (MitM) attacks. Among those impacted are two of the largest global banks - Bank of America and HSBC - as well as one of the world's most popular VPN providers, TunnelBear.

"Our tests find that apps from some of the world's largest banks contain the flaw, which if exploited, could enable an attacker to decrypt, view and modify traffic - including log-in credentials - from the users of the app," write Chris Mcmahon Stone, Tom Chothia, and Flavio Garcia of University of Birmingham, who detailed the discovery in a paper released yesterday.

The findings came as part of a study involving a new blackbox automated-testing mechanism the team came up with to find applications that implement TLS certificate-pinning but fail to verify the hostname, leaving them open to MitM attacks. Dubbed Spinner, the tool uses the Censys Internet scanning engine to scale up what has in the past been a costly, manual process to check. As a part of the release of their paper, the researchers also released Spinner under a Creative Commons License.

The initial discovery of the nine applications came by way of a study using Spinner of 400 iOS and Android applications. All of this sample set control a high degree of sensitive data or transactions, including banking, stock trading, cryptocurrency, and VPN apps.

This latest discovery shines new spotlight on the risks posed by insecurely developed and implemented mobile applications. The stakes are growing for mobile apps, as they're increasingly leveraged for high-risk and high-value transactions in finance, healthcare, manufacturing, and other areas. Unfortunately, the culture and maturity of appsec practices within the mobile app development field has not kept up with the growing risk profile of these apps.

Just last week, High-Tech Bridge released a study that showed among the top 30 cryptocurrency apps on Google Play with 500,000 installations or more, 94% contained at least three medium-risk vulnerabilities and 77% contained at least two high-risk vulnerabilities.

In a good news-bad news analysis of the situation, Ilia Kolochenko, CEO of High-Tech Bridge, explains that vulnerabilities like the one University of Birmingham researchers found and his own team found are still not as alluring as other lower-hanging fruit.

"In most of the cases, exploitation of a mobile app vulnerability requires some pre-existing conditions, such as an already installed malicious app on the same device or attacker's access to the victim’s data channel" such as public wi-fi, Kolochenko says. "All of this makes mobile apps a not-very attractive target for cybercriminals, who would rather target the mobile backend."

As he explains, the bad news is that mobile app vulnerabilities are just the tip of the iceberg in terms of mobile risk exposure, as attacks against APIs and Web services are easier for attackers to scale and just as prevalent in the deployment of mobile apps. The firm's study found that 77% of cryptocurrency applications did not have any hardening or protection of their backend. This isn't just a cryptocurrency app problem.

It is rampant elsewhere: The sloppy level of care with APIs was in clear evidence with a different report published by researchers with Appthority a few weeks ago. They found a vulnerability where a contingent of developers using the Twilio REST API or SDK were hardcoding credentials in mobile apps: Appthority found 170 apps in official app stores were affected by the vulnerability, with millions of users at risk in that case.

It's a disconcerting trend given the acceleration of financial management via mobile devices worldwide. Take Bank of America, which was one of the organizations named in this research. In the case of this particular vulnerability discovery, researchers found the flaw not in the main Bank of America banking app but in its Bank of America Health app, designed for managing HSA accounts. Researchers estimate this particular app racked up between 100,000 to 500,000 installs during its lifecycle--Bank of America says that it updated the app on disclosure from the researchers and has since retired the app with a new version . Mobile banking is increasingly a lynchpin of B of A's future strategy, with mobile usage among its banking customers growing 19% year-over-year, and traffic at its financial centers dwindling by 4%. At this point, nearly a quarter of all of its deposits are now made through mobile devices, according to recent reports.  And that's just within mainline banking--other lines of business like those supported by the vulnerable health app are also going mobile.

This is an industry-wide trend for financial management.According to analysts with App Annie, the number of app sessions initiated in the US has increased by 50% since 2014, up to 22 billion last year. It all goes to prove that the stakes keep growing and so does the mobile attack surface for firms dealing in mobile financial management.

Related Content:

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Truths About BEC Scams
Ericka Chickowski, Contributing Writer,  6/13/2019
DNS Firewalls Could Prevent Billions in Losses to Cybercrime
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/13/2019
Cognitive Bias Can Hamper Security Decisions
Kelly Sheridan, Staff Editor, Dark Reading,  6/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12855
PUBLISHED: 2019-06-16
In words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP support did not verify certificates when used with TLS, allowing an attacker to MITM connections.
CVE-2013-7472
PUBLISHED: 2019-06-15
The "Count per Day" plugin before 3.2.6 for WordPress allows XSS via the wp-admin/?page=cpd_metaboxes daytoshow parameter.
CVE-2019-12839
PUBLISHED: 2019-06-15
In OrangeHRM 4.3.1 and before, there is an input validation error within admin/listMailConfiguration (txtSendmailPath parameter) that allows authenticated attackers to achieve arbitrary command execution.
CVE-2019-12840
PUBLISHED: 2019-06-15
In Webmin through 1.910, any user authorized to the "Package Updates" module can execute arbitrary commands with root privileges via the data parameter to update.cgi.
CVE-2019-12835
PUBLISHED: 2019-06-15
formats/xml.cpp in Leanify 0.4.3 allows for a controlled out-of-bounds write in xml_memory_writer::write via characters that require escaping.