This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Top 10 2014-I7 Insecure Mobile Interface"
Craig Smith (talk | contribs) |
Craig Smith (talk | contribs) |
||
| Line 27: | Line 27: | ||
A secure mobile interface requires: | A secure mobile interface requires: | ||
# Default passwords and ideally default usernames to be changed during initial setup | # Default passwords and ideally default usernames to be changed during initial setup | ||
| − | # Ensuring user accounts can not be enumerated using functionality such as password reset mechanisms | + | # Ensuring user accounts can not be enumerated using functionality such as password reset mechanisms |
| − | # Ensuring account lockout after an appropriate number of tries | + | # Ensuring account lockout after an appropriate number of tries |
| − | # Ensuring credentials are not exposed while connected to wireless networks | + | # Ensuring credentials are not exposed while connected to wireless networks |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2013|language=en}} | ||
'''Scenario #1:''' Password reset indicates whether account exist or not. | '''Scenario #1:''' Password reset indicates whether account exist or not. | ||
Revision as of 21:59, 5 February 2015
| Threat Agents | Attack Vectors | Security Weakness | Technical Impacts | Business Impacts | |
|---|---|---|---|---|---|
| Application Specific | Exploitability AVERAGE |
Prevalence COMMON |
Detectability EASY |
Impact SEVERE |
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?
The easiest way to determine if your mobile interface is secure is by reviewing areas such as account enumeration, account lockout and whether credentials are exposed while connected to wireless networks. |
How Do I Secure My Mobile Interface?
A secure mobile interface requires:
|
|
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.
|
References
OWASP External |
