Difference between revisions of "Germany/Projekte/Top 10-2013-A5-Sicherheitsrelevante Fehlkonfiguration"

From OWASP
Jump to: navigation, search
(Import vom engl. Wiki, mit language=de)
 
m (Top_10_2010:SummaryTableHeaderBeginTemplate|type=images => mit Bildern)
 
Line 14: Line 14:
 
}}
 
}}
  
{{Top_10_2010:SummaryTableHeaderBeginTemplate|year=2013|language=de}}
+
{{Top_10_2010:SummaryTableHeaderBeginTemplate|type=images|year=2013|language=de}}
 
  {{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=1|impact=2|year=2013|language=de}}
 
  {{Top_10:SummaryTableTemplate|exploitability=1|prevalence=2|detectability=1|impact=2|year=2013|language=de}}
 
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}}
 
{{Top_10_2010:SummaryTableHeaderEndTemplate|year=2013}}

Latest revision as of 17:28, 15 June 2013

BAUSTELLE! Hier entsteht das deutsche Wiki der OWASP Top 10-2013

← A4-Unsichere direkte Objektreferenzen
2013 Inhaltsverzeichnis

2013 Die Top-10-Risiken

A6-Verlust der Vertraulichkeit sensibler Daten →
Bedrohungsquelle
Angriffsvektor
Schwachstellen
Technische Auswirkung
Auswirkung auf das Unternehmen
Application Specific Ausnutzbarkeit
EINFACH
Verbreitung
HÄUFIG
Auffindbarkeit
EINFACH
Auswirkung
MITTEL
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.
Bin ich durch 'Sicherheitsrelevante Fehlkonfiguration' verwundbar?
  1. Is your application missing the proper security hardening across any part of the application stack? Including:
  2. Is any of your software out of date? This includes the OS, Web/App Server, DBMS, applications, and all code libraries (see new A9).
  3. Are any unnecessary features enabled or installed (e.g., ports, services, pages, accounts, privileges)?
  4. Are default accounts and their passwords still enabled and unchanged?
  5. Does your error handling reveal stack traces or other overly informative error messages to users?
  6. Are the security settings in your development frameworks (e.g., Struts, Spring, ASP.NET) and libraries not set to secure values?

Without a concerted, repeatable application security configuration process, systems are at a higher risk.

Wie kann ich 'Sicherheitsrelevante Fehlkonfiguration' verhindern?

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 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. Consider running scans and doing audits periodically to help detect future misconfigurations or missing patches.

Mögliche Angriffsszenarien

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.

Referenzen

OWASP

For additional requirements in this area, see the ASVS requirements area for Security Configuration (V12).

Andere

← A4-Unsichere direkte Objektreferenzen
2013 Inhaltsverzeichnis

2013 Die Top-10-Risiken

A6-Verlust der Vertraulichkeit sensibler Daten →

© 2002-2013 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. Some rights reserved. CC-by-sa-3 0-88x31.png