Top 10 2014-I6 Insecure Cloud Interface

From OWASP
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
AVERAGE
Prevalence
COMMON
Detectability
EASY
Impact
SEVERE
Application / Business Specific
Consider anyone who has access to the internet. Attacker uses multiple vectors such as insufficient authentication, lack of transport encryption and account enumeration to access data or controls via the cloud website. Attack will most likely come from the internet. An insecure cloud interface is present when easy to guess credentials are used or account enumeration is possible. Insecure cloud interfaces are easy to discover by simply reviewing the connection to the cloud interface 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 cloud interface could lead to compromise of user data and control over the device. Consider the business impact of an insecure cloud interface. Data could be stolen or modified and control over devices assumed. Could your customers be harmed? Could your brand be harmed?
Is My Cloud Interface Secure?

Checking for a Insecure Cloud 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 the interface for issues such as cross-site scripting, cross-site request forgery and sql injection.
  • Reviewing all cloud interfaces for vulnerabilities (API interfaces and cloud-based web interfaces)
How Do I Secure My Cloud Interface?

A secure cloud 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 3- 5 failed login attempts
  4. Ensuring the cloud-based web interface is not susceptible to XSS, SQLi or CSRF
  5. Ensuring credentials are not exposed over the internet
  6. Implement two factor authentication if possible

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 is valid.

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