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"
| Line 50: | Line 50: | ||
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=4|risk=5|year=2013}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|number=4|risk=5|year=2013}} | ||
{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | ||
| − | * OWASP Development Guide: Chapter on Configuration | + | * [https://www.owasp.org/index.php/Configuration OWASP Development Guide: Chapter on Configuration] |
| − | * OWASP Code Review Guide: Chapter on Error Handling | + | * [https://www.owasp.org/index.php/Error_Handling OWASP Code Review Guide: Chapter on Error Handling] |
| − | * OWASP Testing Guide: Configuration Management | + | * [https://www.owasp.org/index.php/Testing_for_configuration_management OWASP Testing Guide: Configuration Management] |
| − | * OWASP Testing Guide: Testing for Error Codes | + | * [https://www.owasp.org/index.php/Testing_for_Error_Code_(OWASP-IG-006) OWASP Testing Guide: Testing for Error Codes] |
| − | * OWASP Top 10 2004 - Insecure Configuration Management | + | * [https://www.owasp.org/index.php/A10_2004_Insecure_Configuration_Management OWASP Top 10 2004 - Insecure Configuration Management ] |
| + | |||
| + | For additional requirements in this area, see the [https://www.owasp.org/index.php/ASVS ASVS requirements area for Security Configuration (V12)]. | ||
| − | |||
{{Top_10_2010:SubSubsectionExternalReferencesTemplate}} | {{Top_10_2010:SubSubsectionExternalReferencesTemplate}} | ||
| − | * PC Magazine Article on Web Server Hardening | + | * [http://www.pcmag.com/article2/0,2817,11525,00.asp PC Magazine Article on Web Server Hardening] |
| − | * CWE Entry 2 on Environmental Security Flaws | + | * [http://cwe.mitre.org/data/definitions/2.html CWE Entry 2 on Environmental Security Flaws] |
| − | * CIS Security Configuration Guides/Benchmarks | + | * [http://benchmarks.cisecurity.org/downloads/benchmarks/ CIS Security Configuration Guides/Benchmarks] |
{{Top_10_2013:BottomAdvancedTemplate | {{Top_10_2013:BottomAdvancedTemplate | ||
Revision as of 01:52, 5 March 2013
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
| [[Top 10 {{{year}}}-Insecure Direct Object References|← Insecure Direct Object References]] | [[Top_10_{{{year}}}-Top 10|{{{year}}} Top 10 List]] |
[[Top 10 {{{year}}}-Sensitive Data Exposure|Sensitive Data Exposure →]] |
| 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, framework, and custom code. Developers and network 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. | Such flaws frequently give attackers unauthorized access to some system data or functionality. Occasionally, such flaws result in a complete system compromise. | 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'?
Have you performed the proper security hardening across the entire application stack?
A concerted, repeatable process is required to develop and maintain a proper application security configuration. |
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 reverses 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 |
| [[Top 10 {{{year}}}-Insecure Direct Object References|← Insecure Direct Object References]] | [[Top_10_{{{year}}}-Top 10|{{{year}}} Top 10 List]] |
[[Top 10 {{{year}}}-Sensitive Data Exposure|Sensitive Data Exposure →]] |
