Skip to content
This repository was archived by the owner on Apr 17, 2023. It is now read-only.

Files

Latest commit

author
Wei Li
add review of mobile banking review
Aug 24, 2017
73017ec · Aug 24, 2017

History

History
27 lines (24 loc) · 2.54 KB

mobileBankingSecurity.adoc

File metadata and controls

27 lines (24 loc) · 2.54 KB

Mobile Banking Applications Security Challenges

This is a summary of the Mobile Banking Applications Security Challenges report.

Vulnerabilities

  1. World-Writable Files

    1. Creating worldwritable files is a security risk as it could allow other apps to have write access to files, leading to potential security gaps

  2. Broken SSL Check / Sensitive Data in Transit

    1. Lack of proper certificate validation could result in sensitive data being intercepted via a man-in-the-middle attack. Especially on Android.

  3. Writable Executables

    1. A writable executable file is not a vulnerability all by itself, but in combination with another issue could lead to additional app vulnerabilities and make the app susceptible to remote code execution. Android only.

  4. Obfuscation

    1. Intellectual property could be at risk because these apps can easily be reverse-engineered

  5. SecureRandom

    1. Apps which use the Oracle® Java Cryptography Architecture (JCA) for key generation, signing, or random number generation may not receive cryptographically strong values on Android™ devices due to improper initialization of the pseudo-random number generator (PRNG).

    2. Apps that directly invoke the system-provided OpenSSL PRNG without explicit initialization on Android™ are also affected.

  6. Dynamic Code Loading

    1. Typically, core components and additional dependencies are loaded natively at runtime, however, dynamically loaded components are only loaded as requested

  7. Cookie "HttpOnly"

    1. When a cookie is set with the HTTPOnly flag, it instructs the browser that the cookie can only be accessed by the server and not by client-side scripts.

  8. Cookie "Secure" Tag

    1. When set to true, the "secure" flag tells the browser to only send the cookie if the request is sent using a secure channel.

  9. Transport Layer Security Traffic with Sensitive Data

    1. Sending sensitive data without certificate pinning creates higher risk as an attacker with network privileges, or who has compromised TLS, is better positioned to intercept data

  10. App Transport Security

    1. It is on by default when an app is linked to iOS® 9.0 SDK (Software Development Kit) or later.