Difference between revisions of "Germany/Projekte/Top 10 fuer Entwickler-2013/A9-Benutzen von Komponenten mit bekannten Schwachstellen"

From OWASP
Jump to: navigation, search
m (dotNET => .NET (headertabs kann jetzt auch Sonderzeichen darstellen))
m (Navigation angepasst + neue Navigation für HeaderTabs desselben Typ)
Line 1: Line 1:
{{Top_10_2010_Developer_Edition_De:TopTemplate
+
{{Top_10_2013_DeveloperEdition:TopTemplate
     |useprev=PrevLink_Germany_Projekte
+
     |useprev=2013PrevLinkDeveloperEdition
     |usenext=NextLink_Germany_Projekte
+
     |usenext=2013NextLinkDeveloperEdition
     |prev=Top_10_fuer_Entwickler/A8_{{Top_10_2010:ByTheNumbers
+
     |prev=A8-{{Top_10_2010:ByTheNumbers
 
               |8
 
               |8
               |language=de
+
               |year=2013
               |year=2010}}
+
               |language=de}}
     |next=Top_10_fuer_Entwickler/A10_{{Top_10_2010:ByTheNumbers
+
     |next=A10-{{Top_10_2010:ByTheNumbers
 
               |10
 
               |10
               |language=de
+
               |year=2013
               |year=2010}}
+
               |language=de}}
 +
    |year=2013
 
     |language=de
 
     |language=de
    |year=2010
 
 
}}
 
}}
==TEST-TEST TEST -- Seite in Bearbeitung (BAUSTELLE!!) TEST-TEST TEST==
 
 
  
 
==A9 Benutzen von Komponenten mit bekannten Schwachstellen==  
 
==A9 Benutzen von Komponenten mit bekannten Schwachstellen==  
Line 87: Line 85:
 
* [http://www.sonatype.com/content/download/1025/10060/file/sonatype_executive_security_brief_final.pdf  Addressing Security Concerns in Open Source Components]
 
* [http://www.sonatype.com/content/download/1025/10060/file/sonatype_executive_security_brief_final.pdf  Addressing Security Concerns in Open Source Components]
 
* [http://cve.mitre.org/  MITRE Common Vulnerabilities and Exposures]
 
* [http://cve.mitre.org/  MITRE Common Vulnerabilities and Exposures]
 
+
{{Top_10:SubsectionTableEndTemplate}} {{Top 10 DeveloperEdition:NavigationByHeadertab
{{Top_10:SubsectionTableEndTemplate}}
+
    |headertab=JAVA
 
+
    |useprev=2013PrevHeaderTabDeveloperEdition
 +
    |usenext=2013NextHeaderTabDeveloperEdition
 +
    |prev=A8-{{Top_10_2010:ByTheNumbers
 +
              |8
 +
              |year=2013
 +
              |language=de}}
 +
    |next=A10-{{Top_10_2010:ByTheNumbers
 +
              |10
 +
              |year=2013
 +
              |language=de}}
 +
    |year=2013
 +
    |language=de
 +
}}
  
 
= '''.NET''' =   
 
= '''.NET''' =   
Line 122: Line 132:
 
{{Top_10_2010:SubSubsectionExternalReferencesTemplate|year=2013|language=de}}
 
{{Top_10_2010:SubSubsectionExternalReferencesTemplate|year=2013|language=de}}
 
* tbd!!
 
* tbd!!
{{Top_10:SubsectionTableEndTemplate}}
+
{{Top_10:SubsectionTableEndTemplate}} {{Top 10 DeveloperEdition:NavigationByHeadertab
 
+
    |headertab=.NET
 +
    |useprev=2013PrevHeaderTabDeveloperEdition
 +
    |usenext=2013NextHeaderTabDeveloperEdition
 +
    |prev=A8-{{Top_10_2010:ByTheNumbers
 +
              |8
 +
              |year=2013
 +
              |language=de}}
 +
    |next=A10-{{Top_10_2010:ByTheNumbers
 +
              |10
 +
              |year=2013
 +
              |language=de}}
 +
    |year=2013
 +
    |language=de
 +
}}
  
 
= '''Test''' =
 
= '''Test''' =
Line 151: Line 174:
  
 
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=left|risk=9|year=2013|language=de}}
 
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=left|risk=9|year=2013|language=de}}
{{Top_10:SubsectionTableEndTemplate}}
+
{{Top_10:SubsectionTableEndTemplate}} {{Top 10 DeveloperEdition:NavigationByHeadertab
 
+
    |headertab=Test
 +
    |useprev=2013PrevHeaderTabDeveloperEdition
 +
    |usenext=2013NextHeaderTabDeveloperEdition
 +
    |prev=A8-{{Top_10_2010:ByTheNumbers
 +
              |8
 +
              |year=2013
 +
              |language=de}}
 +
    |next=A10-{{Top_10_2010:ByTheNumbers
 +
              |10
 +
              |year=2013
 +
              |language=de}}
 +
    |year=2013
 +
    |language=de
 +
}}
 
<headertabs />
 
<headertabs />
 
+
{{Top_10_2013_DeveloperEdition:BottomAdvancedTemplate
{{Top_10_2010_Developer_Edition_De:BottomAdvancedTemplate
+
 
     |type=0
 
     |type=0
     |useprev=PrevLink_Germany_Projekte
+
     |useprev=2013PrevLinkDeveloperEdition
     |usenext=NextLink_Germany_Projekte
+
     |usenext=2013NextLinkDeveloperEdition
     |prev=Top_10_fuer_Entwickler/A8_{{Top_10_2010:ByTheNumbers
+
     |prev=A8-{{Top_10_2010:ByTheNumbers
 
               |8
 
               |8
               |language=de
+
               |year=2013
               |year=2010}}
+
               |language=de}}
     |next=Top_10_fuer_Entwickler/A10_{{Top_10_2010:ByTheNumbers
+
     |next=A10-{{Top_10_2010:ByTheNumbers
 
               |10
 
               |10
               |language=de
+
               |year=2013
               |year=2010}}
+
               |language=de}}
 +
    |year=2013
 
     |language=de
 
     |language=de
    |year=2010
 
 
}}
 
}}
 
[[Category:OWASP Top 10 fuer Entwickler]]
 

Revision as of 06:29, 17 July 2013

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

← A8-Cross-Site Request Forgery (CSRF)
Top 10 fuer Entwickler-2013: Inhaltsverzeichnis

Die Top-10-Risiken

A10-Ungeprüfte Um- und Weiterleitungen →

A9 Benutzen von Komponenten mit bekannten Schwachstellen

Bedrohungsquelle
Angriffsvektor
Schwachstellen
Technische Auswirkung
Auswirkung auf das Unternehmen
Application Specific Ausnutzbarkeit
DURCHSCHNITTLICH
Verbreitung
SEHR HÄUFIG
Auffindbarkeit
SCHWIERIG
Auswirkung
MITTEL
Application / Business Specific
Some vulnerable components (e.g., framework libraries) can be identified and exploited with automated tools, expanding the threat agent pool beyond targeted attackers to include chaotic actors. Attacker identifies a weak component through scanning or manual analysis. They customize the exploit as needed and execute the attack. It gets more difficult if the used component is deep in the application. Virtually every application has these issues because most development teams don’t focus on ensuring their components stay up to date. In many cases, the developers don’t even know all the components they are using, never mind their versions. Component dependencies make things even worse. The full range of weaknesses is possible, including injection, broken access control, XSS, etc. The impact could be minimal, up to complete host takeover and data compromise. Consider what each vulnerability might mean for the business controlled by the affected application. It could be trivial or it could mean complete compromise.
Mögliche Angriffsszenarien

Component vulnerabilities can cause almost any type of risk imaginable, from the trivial to sophisticated malware designed to target a specific organization. Components almost always run with the full privilege of the application, so flaws in any component can be serious, The following two vulnerable components were downloaded 22m times in 2011.

  • Apache CXF Authentication Bypass – By failing to provide an identity token, attackers could invoke any web service with full permission.
  • Spring Remote Code Execution– Abuse of the Expression Language implementation in Spring allowed attackers to execute arbitrary code, effectively taking over the server.

Every application using either of these vulnerable libraries is vulnerable to attack as both of these components are directly accessible by application users. Other vulnerable libraries, used deeper in an application, may be harder to exploit.

Wie kann ich 'Benutzen von Komponenten mit bekannten Schwachstellen' verhindern?

One option is not to use components that you didn’t write. But realistically, the best way to deal with this risk is to ensure that you keep your components up-to-date. Many open source projects (and other component sources) do not create vulnerability patches for old versions. Instead, most simply fix the problem in the next version. Software projects should have a process in place to:

  1. Identify the components and their versions you are using, including all dependencies. (e.g., the versions plugin).
  2. Monitor the security of these components in public databases, project mailing lists, and security mailing lists, and keep them up-to-date.
  3. Establish security policies governing component use, such as requiring certain software development practices, passing security tests, and acceptable licenses.
[edit]

Verteidigungs-Option 1 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd
tbd

Verteidigungs-Option 2 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd

tbd
tbd
Verteidigungs-Option 3 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd

tbd
tbd
Referenzen

OWASP

Andere

Verteidigungs-Option 1 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd
tbd

Verteidigungs-Option 2 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd

tbd
tbd
Verteidigungs-Option 3 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

Tbd

tbd

tbd
tbd
Referenzen

OWASP

  • tbd !!

Andere

  • tbd!!

Verteidigungs-Option 1 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

tbd Text

Verteidigungs-Option 2 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

tbd Text

Verteidigungs-Option 3 gegen 'Benutzen von Komponenten mit bekannten Schwachstellen':

tbd (ganze Breite) Text

Auswirkung(en) auf den Benutzer

Text

Wie kann ich 'Benutzen von Komponenten mit bekannten Schwachstellen' verhindern?

Text

Referenzen

← A8-Cross-Site Request Forgery (CSRF)
Top 10 fuer Entwickler-2013: Inhaltsverzeichnis

Die Top-10-Risiken

A10-Ungeprüfte Um- und Weiterleitungen →

© 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