This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Top 10 2014-I7 Insecure Mobile Interface

Jump to: navigation, search
Back To The Internet of Things Top 10
Threat Agents Attack Vectors Security Weakness Technical Impacts Business Impacts
Application Specific Exploitability
Application / Business Specific
Consider anyone who has access to the mobile application. Attacker uses multiple vectors such as insufficient authentication, lack of transport encryption and account enumeration to access data or controls via the mobile interface. An insecure mobile interface is present when easy to guess credentials are used or account enumeration is possible. Insecure mobile interfaces are easy to discover by simply reviewing the connection to the wireless networks and identifying if SSL is in use or by using the password reset mechanism to identify valid accounts which can lead to account enumeration. An insecure mobile interface could lead to compromise of user data and control over the device. Consider the business impact of an insecure mobile interface. Data could be stolen or modified and control over devices assumed. Could your customers be harmed? Could your brand be harmed?
Is My Mobile Interface Secure?

Checking for an Insecure Mobile Interface includes:

  • Determining if the default username and password can be changed during initial product setup
  • Determining if a specific user account is locked out after 3 - 5 failed login attempts
  • Determining if valid accounts can be identified using password recovery mechanisms or new user pages
  • Reviewing whether credentials are exposed while connected to wireless networks
  • Reviewing whether two factor authentication options are available
How Do I Secure My Mobile Interface?

A secure mobile interface requires:

  1. Default passwords and ideally default usernames to be changed during initial setup
  2. Ensuring user accounts can not be enumerated using functionality such as password reset mechanisms
  3. Ensuring account lockout after an 3 - 5 failed login attempts
  4. Ensuring credentials are not exposed while connected to wireless networks
  5. Implementing two factor authentication if possible
  6. Apply mobile app obfuscation techinque
  7. Implement mbile app anti-tempering mechanism
  8. Ensuring the mobile app's memory hacking is possible
  9. Restric the mobile app's execution on tempered OS environment

Please review the following tabs for more detail based on whether you are a Manufacturer, Developer or Consumer

Example Attack Scenarios

Scenario #1: Password reset indicates whether account exist or not.

Password Reset "That account does not exist."

Scenario #2: Username and password are poorly protected when transmitted over the network.

Authorization: Basic S2ZjSDFzYkF4ZzoxMjM0NTY3

In the cases above, the attacker is able to either determine a valid user account or is able to capture the credentials as they cross the network and decode them since the credentials are only protected using Base64 Encoding.



OWASP Top Ten Mobile Risks