Top 10 2014-I9 Insecure Software/Firmware Updates

Back To The Internet of Things Top 10

Consider anyone who has access to the device and the network the device is connected to.

Attacker uses multiple vectors such as capturing update files via unencrypted connections, the update file itself is not encrypted or they are able to perform their own malicious update via DNS hijacking. Depending on method of update and device configuration, attack could come from the local network or the internet.

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?

TEXT

Ensuring a secure mobile interface requires:
 * 1) Ensuring ...
 * 2) Ensuring ...
 * 3) Ensuring ...
 * 4) Ensuring ...

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.