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.

Application Security

Major Mobile Financial Apps Harbor Built-in Vulnerabilities

A wide variety of financial services companies' apps suffer from poor programing practices and unshielded data.

Mobile apps for financial services are an important part of many consumers' financial lives, yet those apps are suffering a "vulnerability epidemic," according to a new report.

The report, commissioned by Arxan and produced by the Aite Group, looks at the perceived security of mobile financial apps versus the reality. And in many cases, to quote a movie title from 1994, "Reality Bites."

The report is based on research conducted by Aite Group researcher Alissa Knight that decompiled the apps to their original source code for vulnerability assessment. For many of the apps, that step started the list of vulnerabilities, since application shielding should prevent threat actors from decompiling an application to do their own vulnerability assessment.

"Mobile apps in general lack the necessary security features to protect users data. Even with social engineering and mobile breaches occurring more often, app developers still are not developing apps with security in mind," says Timur Kovalev, chief technology officer at Untangle.

Because the apps come from trusted financial institutions, consumers begin with the assumption that they are secure. "While users are comfortable using mobile apps for nearly anything and everything these days, the concerns for securing their money and financial information can make nearly anyone a little hesitant. And maybe with good reason," says Nathan Wenzler, senior director of cybersecurity at Moss Adams, a Seattle-based accounting, consulting, and wealth management firm.

Wenzler points out that the players in the market are broadly divided between traditional financial institutions which are known for their legacy of security but often have woeful inexperience with agile app development and newer online financial institutions that who have less experience in the regulatory and security requirements in the financial sector, but have access to modern secure development methods.

Those differences in experience and expertise are borne out in the critical vulnerabilities found in the mobile apps: Retail banking apps have the greatest number of critical vulnerabilities, while the greatest number of severe findings came from auto insurance apps, which contained the most hard-coded private keys, API keys, and secrets in their code.

Other common vulnerabilities found in code across all sectors are hard-coded SQL statements and hard-coded private certificates that a threat actor could easily replaced and code around. 

The most secure mobile financial apps are those of banks that offer and service health savings accounts (HSAs), followed by health insurer mobile payment apps, and credit card issuers. Whether their apps are on the more or less vulnerable end of the scale, Wenzler says that institutions across the industry know that they must improve application security. "No matter who is providing the financial services, everyone [in the industry] realizes what's at stake when to comes to their customers and their finances."

Kovalev says that financial services companies should improve the security performance of their own development organizations while working with other organizations to boost security even further. "It is critical that developers start taking app security seriously and that app stores like Google Play Store and Apple App Store enforce stricter security standards for apps that have access to such sensitive data," he says.

Wenzler is adamant that a failure to improve mobile financial app security could have huge consequences for banks and financial services companies. "Unlike many non-financial businesses, these banks won't recover as easily from a breach of trust over their customer's finances," he says. And those financial services firms supporting mobile applications have a huge challenge in front of them, Wenzler says, since most start from a position of relative insecurity.

"Making application security an integral part of the development and DevOps processes is critical to creating confidence within the customer base that their money and information is secure, no matter how they choose to manage their banking tasks," he says.

Related Content:

 

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
UdyRegan
50%
50%
UdyRegan,
User Rank: Apprentice
4/9/2019 | 4:36:30 AM
Starts from apps
It is scary to know that financial apps do not have the necessary tight security that we would expect. Users input sensitive data into such apps daily and we would require maximum security and nothing less. So much can be done from first level apps which could propose more critical risks.
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-1817
PUBLISHED: 2019-11-20
MediaWiki before 1.19.4 and 1.20.x before 1.20.3 contains an error in the api.php script which allows remote attackers to obtain sensitive information.
CVE-2013-2091
PUBLISHED: 2019-11-20
SQL injection vulnerability in Dolibarr ERP/CRM 3.3.1 allows remote attackers to execute arbitrary SQL commands via the 'pays' parameter in fiche.php.
CVE-2012-1257
PUBLISHED: 2019-11-20
Pidgin 2.10.0 uses DBUS for certain cleartext communication, which allows local users to obtain sensitive information via a dbus session monitor.
CVE-2013-1816
PUBLISHED: 2019-11-20
MediaWiki before 1.19.4 and 1.20.x before 1.20.3 allows remote attackers to cause a denial of service (application crash) by sending a specially crafted request.
CVE-2011-4455
PUBLISHED: 2019-11-20
Multiple cross-site scripting vulnerabilities in Tiki 7.2 and earlier allow remote attackers to inject arbitrary web script or HTML via the path info to (1) tiki-admin_system.php, (2) tiki-pagehistory.php, (3) tiki-removepage.php, or (4) tiki-rename_page.php.