More than half of banking applications from the App Store and Google Play have security holes

Источник изображения: Jonas Leupe / unsplash.com

A security analysis of 2,686 mobile banking apps revealed serious flaws that could leave customers vulnerable to cybercriminals and financial fraudsters. Among the shortcomings are private keys and credentials stored in open form, as well as the lack of basic security measures.

  Image source: Jonas Leupe / unsplash.com

Image source: Jonas Leupe / unsplash.com

Ostorlab experts studied applications of 487 banks from 64 countries for the mobile platforms Google Android, Apple iOS and Huawei HarmonyOS. More than half of them were found to have critical or serious vulnerabilities, raising concerns about the reliability of mobile financial transactions. 51.5% of the software products studied, which is 1384 units, have at least one high or critical level vulnerability. At the same time, 18.4% of applications received a critical rating during automated security testing.

Biometric authentication raises questions, especially in Android applications, where vulnerabilities have been identified affecting fingerprint and facial recognition systems. In 35.1% of the Android programs studied, scanning tools were able to bypass biometric verification tools – despite the fact that in 73.2% of cases, biometric authentication was tied to encryption keys. Another problem is storing sensitive credentials inside application packages, which makes available information that should be hidden from outsiders.

In 20.3% of applications (544 banking products), Ostorlab specialists found private keys, credentials for cloud services, and access tokens for software services. Google API keys were found in 72.5% of applications, although the mere fact of their presence does not indicate that credentials have been compromised. Such keys are commonly used to operate services, including Google Maps and Firebase, although without proper restrictions, attackers can use the resources associated with them for their own purposes.

  Image source: NordWood / unsplash.com

The study identified outdated software components with known vulnerabilities, which opens up additional opportunities for attacks on applications as a whole. Approximately 41.1% of applications contain at least one vulnerable third-party component, and 18.2% contain components with critical vulnerabilities. Despite security concerns, few banking apps use modern authentication technologies to reduce the risk of credential theft and unauthorized access to accounts. Only 4.9% of apps support passkey technology, and 20.2% use app or device attestation tools that allow banks to determine whether a customer is using a genuine version of an app. Accordingly, 79.8% of products were deprived of such protection.

Almost a quarter (22.3%) of Android applications were able to recognize remote control or screen sharing tools that are often used by attackers. Commercial or platform-based application protection solutions are present in only 26.9% of Android products. Outdated operating systems pose an additional problem: 99.5% of applications support platforms that no longer receive security updates. As a result, customers using outdated devices continue to receive financial services in a software environment that lacks important security features provided by the developer.

Apps from 192 of the nearly 500 banks appear on public lists of financial institutions targeted by banking malware. This represents 38% of the total number of banks included in the study, although the mere fact of being on such lists does not mean that the applications were successfully attacked.

The results presented, Ostorlab emphasized, should not be taken as a confirmed possibility of carrying out successful attacks – rather, it is “evidence of the existence of a problem, and not proof that this vulnerability can be exploited in real conditions.”

If you notice an error, select it with the mouse and press CTRL+ENTER.