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-I3 Insecure Network Services"

From OWASP
Jump to: navigation, search
 
(23 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=OWASP_Internet_of_Things_Top_10_for_2014 Back To The Internet of Things Top 10]</center>
+
<center>[https://www.owasp.org/index.php/OWASP_Internet_of_Things_Project#tab=Top_10_IoT_Vulnerabilities__282014_29 Back To The Internet of Things Top 10]</center>
  
 
{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}
 
{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=en}}
−
{{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=2|impact=1|year=2013|language=en}}
+
{{Top_10:SummaryTableTemplate|exploitability=2|prevalence=3|detectability=2|impact=2|year=2013|language=en}}
 
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}}
 
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}}
 
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the device via a network connection, including external and internal users.
 
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider anyone who has access to the device via a network connection, including external and internal users.
  
 
</td>
 
</td>
−
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Attacker uses weak passwords, insecure password recovery mechanisms, poorly protected credentials or lack of role/discretionary based access control to access a particular interface. Depending on setup, attack could come from external or internal users.
+
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Attacker uses vulnerable network services to attack the device itself or bounce attacks off the device. Attack could come from external or internal users.
  
 
</td>
 
</td>
−
     <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Authentication/Authorization may not be sufficient when weak passwords are used or are poorly protected. Insufficient authentication/authorization is prevalent as manufacturers strive to make interfaces easier for users to use and assume these interfaces will not be exposed to external users. Deficiencies are often found to be present across all interfaces as vendors strive to make credentials match across varying interfaces. Many Issues with authentication/authorization are easy to discover when examining the interface manually and frequently easy to discover via automated testing.
+
     <td colspan=2  {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insecure network services may be susceptible to buffer overflow attacks or attacks that create a denial of service condition leaving the device inaccessible to the user. Denial of service attacks against other users may also be facilitated when insecure network services are available. Insecure network services can often be detected by automated tools such as port scanners and fuzzers.
  
 
</td>
 
</td>
−
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insufficient authentication/authorization can result in data loss or corruption, lack of accountability, or denial of access and can lead to complete compromise of the device or user accounts.
+
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Insecure network services can result in data loss or corruption, denial of service or facilitation of attacks on other devices.
  
 
</td>
 
</td>
−
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact of compromised devices and accounts and in turn compromised customers. All data could be stolen, modified, or deleted. Could your users be harmed?
+
     <td {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2013}}>Consider the business impact of devices which have been rendered useless from a denial of service attack or the device is used to facilitate attacks against other devices and networks. Could your customers or other users be harmed?
  
 
</td>
 
</td>
Line 22: Line 22:
  
 
{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Are My Network Services Secure?|position=firstLeft|year=2013|language=en}}
 
{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=Are My Network Services Secure?|position=firstLeft|year=2013|language=en}}
−
The simplest way to find out if you have insufficient authorization/authentication is to review the password policy for the various interfaces and to review whether the interfaces allow for separation of roles. For example, all features will be accessible to administrators, but users will have a more limited set of features available.
+
Checking for Insecure Network Services includes:
 +
* Determining if insecure network services exist by reviewing your device for open ports using a port scanner
 +
* As open ports are identified, each can be tested using any number of automated tools that look for DoS vulnerabilities, vulnerabilities related to UDP services and vulnerabilities related to buffer overflow and fuzzing attacks
 +
* Reviewing network ports to ensure they are absolutely necessary and if there are any ports being exposed to the internet using UPnP.
  
−
Attempting to set usernames to simple passwords such as "1234" is a fast and easy way to determine if authentication/authorization is sufficient. Manual testing can help a security analyst find instances where weak passwords are allowed, access control is not limited by roles or credentials are poorly protected. Penetration testers can validate these issues by conducting brute-force attacks against usernames, reviewing access controls and testing for privilege escalation.
+
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Network Services?|position=right|year=2013|language=en}}
 +
Securing network services requires:
 +
# Ensuring only necessary ports are exposed and available.
 +
# Ensuring services are not vulnerable to buffer overflow and fuzzing attacks.
 +
# Ensuring services are not vulnerable to DoS attacks which can affect the device itself or other devices and/or users on the local network or other networks.
 +
# Ensuring network ports or services are not exposed to the internet via UPnP for example
 +
# The abnormal service request traffic should be detected and blocked on service gateway layer
  
−
Automated dynamic scanning which exercises the application will provide insight into whether these issues exist as well.
+
 
−
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|title=How Do I Secure My Network Services?|position=right|year=2013|language=en}}
+
Please review the following tabs for more detail based on whether you are a [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Manufacturers Manufacturer], [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Developers Developer] or [https://www.owasp.org/index.php/OWASP_Internet_of_Things_Top_Ten_Project#tab=Consumers Consumer]
−
Ensuring sufficient authentication/authorization requires:
 
−
# Ensuring password recovery mechanisms are robust.
 
−
# Ensuring complex password construction.
 
−
# Ensuring role/discretionary based access control is in place where necessary.
 
−
# Ensuring credentials are properly protected.
 
 
{{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:''' Fuzzing attack causes network service and device to crash.
  
 
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
 
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
−
Username = Bob; Password = 1234
+
GET %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s HTTP/1.0
  
 
</span>{{Top_10_2010:ExampleEndTemplate}}
 
</span>{{Top_10_2010:ExampleEndTemplate}}
−
'''Scenario #2:''' Username and password are poorly protected when transmitted over the network.
+
'''Scenario #2:''' Ports open to the internet possibly without the user's knowledge via UPnP.
 
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
 
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;">
−
Authorization: Basic YWRtaW46MTIzNA==
+
Port 80 and 443 exposed to the internet via a home router.
  
 
</span>{{Top_10_2010:ExampleEndTemplate}}
 
</span>{{Top_10_2010:ExampleEndTemplate}}
−
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.
+
In the cases above, the attacker is able to disable the device completely with an HTTP GET or access the device via the internet over port 80 and/or port 443.
  
  

Latest revision as of 05:56, 5 February 2016

Back To The Internet of Things Top 10
Threat Agents Attack Vectors Security Weakness Technical Impacts Business Impacts
Application Specific Exploitability
AVERAGE		 Prevalence
UNCOMMON		 Detectability
AVERAGE		 Impact
MODERATE		 Application / Business Specific
Consider anyone who has access to the device via a network connection, including external and internal users. Attacker uses vulnerable network services to attack the device itself or bounce attacks off the device. Attack could come from external or internal users. Insecure network services may be susceptible to buffer overflow attacks or attacks that create a denial of service condition leaving the device inaccessible to the user. Denial of service attacks against other users may also be facilitated when insecure network services are available. Insecure network services can often be detected by automated tools such as port scanners and fuzzers. Insecure network services can result in data loss or corruption, denial of service or facilitation of attacks on other devices. Consider the business impact of devices which have been rendered useless from a denial of service attack or the device is used to facilitate attacks against other devices and networks. Could your customers or other users be harmed?
Are My Network Services Secure?

Checking for Insecure Network Services includes:

  • Determining if insecure network services exist by reviewing your device for open ports using a port scanner
  • As open ports are identified, each can be tested using any number of automated tools that look for DoS vulnerabilities, vulnerabilities related to UDP services and vulnerabilities related to buffer overflow and fuzzing attacks
  • Reviewing network ports to ensure they are absolutely necessary and if there are any ports being exposed to the internet using UPnP.
How Do I Secure My Network Services?

Securing network services requires:

  1. Ensuring only necessary ports are exposed and available.
  2. Ensuring services are not vulnerable to buffer overflow and fuzzing attacks.
  3. Ensuring services are not vulnerable to DoS attacks which can affect the device itself or other devices and/or users on the local network or other networks.
  4. Ensuring network ports or services are not exposed to the internet via UPnP for example
  5. The abnormal service request traffic should be detected and blocked on service gateway layer


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

Example Attack Scenarios

Scenario #1: Fuzzing attack causes network service and device to crash.

GET %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s HTTP/1.0

Scenario #2: Ports open to the internet possibly without the user's knowledge via UPnP.

Port 80 and 443 exposed to the internet via a home router.

In the cases above, the attacker is able to disable the device completely with an HTTP GET or access the device via the internet over port 80 and/or port 443.


References

OWASP

External
Retrieved from "https://wiki.owasp.org/index.php?title=Top_10_2014-I3_Insecure_Network_Services&oldid=208168"