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"
From OWASP
Craig Smith (talk | contribs) |
Craig Smith (talk | contribs) |
||
| Line 22: | Line 22: | ||
{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Is My Mobile Interface Secure?|position=firstLeft|year=2013|language=en}} | {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Is My Mobile Interface Secure?|position=firstLeft|year=2013|language=en}} | ||
| − | + | 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. | |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Mobile Interface?|position=right|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Mobile Interface?|position=right|year=2013|language=en}} | ||
Ensuring a secure mobile interface requires: | Ensuring a secure mobile interface requires: | ||
| − | # Ensuring | + | # Ensuring user accounts can not be enumerated using functionality such as password reset mechanims |
| − | # Ensuring | + | # Ensuring account lockout after an appropriate number of tries. |
| − | # Ensuring | + | # 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:''' The interface only requires simple passwords. | '''Scenario #1:''' The interface only requires simple passwords. | ||
Revision as of 01:23, 26 June 2014
| Threat Agents | Attack Vectors | Security Weakness | Technical Impacts | Business Impacts | |
|---|---|---|---|---|---|
| Application Specific | Exploitability EASY |
Prevalence COMMON |
Detectability AVERAGE |
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. Attack will most likely come from a stolen mobile device. | 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 device itself or the cloud interface and identifying if SSL is in use or by attempting to login with random credentials and identifying what errors are returned. Automated tools can also look for issues such as lack of transport encryption and 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 devices taken control of. Could your users 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?
Ensuring a secure mobile interface requires:
|
|
Example Attack Scenarios
Scenario #1: The interface only requires simple passwords. Example Scenario #2: Username and password are poorly protected when transmitted over the network. Example In the cases above, the attacker is able to either easily guess the password or is able to capture the credentials as they cross the network and decode it since the credentials are only protected using Base64 Encoding.
|
References
OWASP External |
