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 2013-A5-Security Misconfiguration"
m (deleted a '#' in Am I Vulerable...; added several '#' at 'How Do I prevent...') |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Top_10_2013:TopTemplate | {{Top_10_2013:TopTemplate | ||
|usenext=2013NextLink | |usenext=2013NextLink | ||
| − | |next={{Top_10_2010:ByTheNumbers | + | |next=A6-{{Top_10_2010:ByTheNumbers |
|6 | |6 | ||
|year=2013 | |year=2013 | ||
|language=en}} | |language=en}} | ||
|useprev=2013PrevLink | |useprev=2013PrevLink | ||
| − | |prev={{Top_10_2010:ByTheNumbers | + | |prev=A4-{{Top_10_2010:ByTheNumbers |
|4 | |4 | ||
|year=2013 | |year=2013 | ||
|language=en}} | |language=en}} | ||
| + | |year=2013 | ||
| + | |language=en | ||
}} | }} | ||
| Line 39: | Line 41: | ||
{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=vulnerableTo|position=firstLeft|risk=5|year=2013|language=en}} | {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=vulnerableTo|position=firstLeft|risk=5|year=2013|language=en}} | ||
| − | + | Is your application missing the proper security hardening across any part of the application stack? Including: | |
# Is any of your software out of date? This includes the OS, Web/App Server, DBMS, applications, and all code libraries (see new A9). | # Is any of your software out of date? This includes the OS, Web/App Server, DBMS, applications, and all code libraries (see new A9). | ||
# Are any unnecessary features enabled or installed (e.g., ports, services, pages, accounts, privileges)? | # Are any unnecessary features enabled or installed (e.g., ports, services, pages, accounts, privileges)? | ||
| Line 50: | Line 52: | ||
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=howPrevent|position=right|risk=5|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=howPrevent|position=right|risk=5|year=2013|language=en}} | ||
The primary recommendations are to establish all of the following: | The primary recommendations are to establish all of the following: | ||
| − | A repeatable hardening process that makes it fast and easy to deploy another environment that is properly locked down. Development, QA, and production environments should all be configured identically (with different passwords used in each environment). This process should be automated to minimize the effort required to setup a new secure environment. | + | # A repeatable hardening process that makes it fast and easy to deploy another environment that is properly locked down. Development, QA, and production environments should all be configured identically (with different passwords used in each environment). This process should be automated to minimize the effort required to setup a new secure environment. |
| − | A process for keeping abreast of and deploying all new software updates and patches in a timely manner to each deployed environment. This needs to include '''all code libraries as well (see new A9)'''. | + | # A process for keeping abreast of and deploying all new software updates and patches in a timely manner to each deployed environment. This needs to include '''all code libraries as well (see new A9)'''. |
| − | A strong application architecture that provides effective, secure separation between components. | + | # A strong application architecture that provides effective, secure separation between components. |
| − | Consider running scans and doing audits periodically to help detect future misconfigurations or missing patches. | + | # Consider running scans and doing audits periodically to help detect future misconfigurations or missing patches. |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=5|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=5|year=2013|language=en}} | ||
| − | + | '''Scenario #1:''' The app server admin console is automatically installed and not removed. Default accounts aren’t changed. Attacker discovers the standard admin pages are on your server, logs in with default passwords, and takes over. | |
| − | + | '''Scenario #2:''' Directory listing is not disabled on your server. Attacker discovers she can simply list directories to find any file. Attacker finds and downloads all your compiled Java classes, which she decompiles and reverse engineers to get all your custom code. She then finds a serious access control flaw in your application. | |
| − | + | '''Scenario #3:''' App server configuration allows stack traces to be returned to users, potentially exposing underlying flaws. Attackers love the extra information error messages provide. | |
| − | + | '''Scenario #4:''' App server comes with sample applications that are not removed from your production server. Said sample applications have well known security flaws attackers can use to compromise your server. | |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=right|risk=5|year=2013|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=right|risk=5|year=2013|language=en}} | ||
{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | ||
| Line 80: | Line 82: | ||
|type={{Top_10_2010:StyleTemplate}} | |type={{Top_10_2010:StyleTemplate}} | ||
|usenext=2013NextLink | |usenext=2013NextLink | ||
| − | |next={{Top_10_2010:ByTheNumbers | + | |next=A6-{{Top_10_2010:ByTheNumbers |
|6 | |6 | ||
|year=2013 | |year=2013 | ||
|language=en}} | |language=en}} | ||
|useprev=2013PrevLink | |useprev=2013PrevLink | ||
| − | |prev={{Top_10_2010:ByTheNumbers | + | |prev=A4-{{Top_10_2010:ByTheNumbers |
|4 | |4 | ||
|year=2013 | |year=2013 | ||
|language=en}} | |language=en}} | ||
| + | |year=2013 | ||
| + | |language=en | ||
}} | }} | ||
Latest revision as of 20:58, 23 June 2013
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
| Threat Agents | Attack Vectors | Security Weakness | Technical Impacts | Business Impacts | |
|---|---|---|---|---|---|
| Application Specific | Exploitability EASY |
Prevalence COMMON |
Detectability EASY |
Impact MODERATE |
Application / Business Specific |
|
Consider anonymous external attackers as well as users with their own accounts that may attempt to compromise the system. Also consider insiders wanting to disguise their actions. |
Attacker accesses default accounts, unused pages, unpatched flaws, unprotected files and directories, etc. to gain unauthorized access to or knowledge of the system. |
Security misconfiguration can happen at any level of an application stack, including the platform, web server, application server, database, framework, and custom code. Developers and system administrators need to work together to ensure that the entire stack is configured properly. Automated scanners are useful for detecting missing patches, misconfigurations, use of default accounts, unnecessary services, etc. |
The system could be completely compromised without you knowing it. All of your data could be stolen or modified slowly over time. Recovery costs could be expensive |
The system could be completely compromised without you knowing it. All your data could be stolen or modified slowly over time. Recovery costs could be expensive. |
|
|
Am I Vulnerable To 'Security Misconfiguration'?
Is your application missing the proper security hardening across any part of the application stack? Including:
Without a concerted, repeatable application security configuration process, systems are at a higher risk. |
How Do I Prevent 'Security Misconfiguration'?
The primary recommendations are to establish all of the following:
|
|
Example Attack Scenarios
Scenario #1: The app server admin console is automatically installed and not removed. Default accounts aren’t changed. Attacker discovers the standard admin pages are on your server, logs in with default passwords, and takes over. Scenario #2: Directory listing is not disabled on your server. Attacker discovers she can simply list directories to find any file. Attacker finds and downloads all your compiled Java classes, which she decompiles and reverse engineers to get all your custom code. She then finds a serious access control flaw in your application. Scenario #3: App server configuration allows stack traces to be returned to users, potentially exposing underlying flaws. Attackers love the extra information error messages provide. Scenario #4: App server comes with sample applications that are not removed from your production server. Said sample applications have well known security flaws attackers can use to compromise your server. |
References
OWASP
For additional requirements in this area, see the ASVS requirements area for Security Configuration (V12). External |
