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
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=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 determine if insecure network services exist is to review your device for open ports using a port scanner such as Nmap. 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. Discovered ports should also be reviewed to ensure they are absolutely necessary and if there are any ports being exposed to the internet using UPnP. | |
{{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}} | {{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}} | ||
| − | Ensuring | + | Ensuring network services are secure requires: |
| − | # Ensuring | + | # Ensuring only necessary ports are exposed and available. |
| − | # Ensuring | + | # Ensuring services are not vulnerable to buffer overflow and fuzzing attacks. |
| − | # Ensuring | + | # Ensuring services are not vulnerable to DoS attacks which can affect the device itself or other devices and/or users on the network. |
| − | |||
{{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:''' | + | '''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;"> | ||
| − | + | 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:''' | + | '''Scenario #2:''' Ports open to the internet possibly without the users knowledge via UPnP. |
{{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | {{Top_10_2010:ExampleBeginTemplate|year=2013}}<span style="color:red;"> | ||
| − | + | Port 80 and 443 exposed to the internet via a home router. | |
</span>{{Top_10_2010:ExampleEndTemplate}} | </span>{{Top_10_2010:ExampleEndTemplate}} | ||
Revision as of 16:13, 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 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. Depending on setup, attack could come from external or internal users. | Insecure network services may be susceptible to buffer overflow attacks or attacks that created 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. 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. | 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. | 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? | |
|
Are My Network Services Secure?
The simplest way to determine if insecure network services exist is to review your device for open ports using a port scanner such as Nmap. 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. Discovered ports should also be reviewed 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?
Ensuring network services are secure requires:
|
|
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 users knowledge via UPnP. Port 80 and 443 exposed to the internet via a home router. 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 |
