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 "Category:OWASP Source Code Flaws Top 10 Project Index"

From OWASP
Jump to: navigation, search
(New page: = The OWASP Source Code Flaws Top 10 =)
 
Line 1: Line 1:
 
= The OWASP Source Code Flaws Top 10 =
 
= The OWASP Source Code Flaws Top 10 =
 +
 +
{| border='1' cellpadding='2'
 +
|-
 +
|[[Source_Code_Flaws_Top_10_2009-C1|C1 - ]]
 +
|XSS flaws occur whenever an application takes user supplied data and sends it to a web browser without first validating or encoding that content. XSS allows attackers to execute script in the victim's browser which can hijack user sessions, deface web sites, possibly introduce worms, etc.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C2|C2 - ]]
 +
|Injection flaws, particularly SQL injection, are common in web applications. Injection occurs when user-supplied data is sent to an interpreter as part of a command or query. The attacker's hostile data tricks the interpreter into executing unintended commands or changing data.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C3|C3 - ]]
 +
|Code vulnerable to remote file inclusion (RFI) allows attackers to include hostile code and data, resulting in devastating attacks, such as total server compromise. Malicious file execution attacks affect PHP, XML and any framework which accepts filenames or files from users.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C4|C4 - ]]
 +
|A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, database record, or key, as a URL or form parameter. Attackers can manipulate those references to access other objects without authorization.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C5|C5 - ]]
 +
|A CSRF attack forces a logged-on victim's browser to send a pre-authenticated request to a vulnerable web application, which then forces the victim's browser to perform a hostile action to the benefit of the attacker. CSRF can be as powerful as the web application that it attacks.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C6|C6 - ]]
 +
|Applications can unintentionally leak information about their configuration, internal workings, or violate privacy through a variety of application problems. Attackers use this weakness to steal sensitive data, or conduct more serious attacks.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C7|C7 - ]]
 +
|Account credentials and session tokens are often not properly protected. Attackers compromise passwords, keys, or authentication tokens to assume other users' identities.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C8|C8 - ]]
 +
|Web applications rarely use cryptographic functions properly to protect data and credentials. Attackers use weakly protected data to conduct identity theft and other crimes, such as credit card fraud.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C9|C9 - ]]
 +
|Applications frequently fail to encrypt network traffic when it is necessary to protect sensitive communications.
 +
|-
 +
 +
|[[Source_Code_Flaws_Top_10_2009-C10|C10 - ]]
 +
|Frequently, an application only protects sensitive functionality by preventing the display of links or URLs to unauthorized users. Attackers can use this weakness to access and perform unauthorized operations by accessing those URLs directly.
 +
|}
 +
'''<center>Table 1: Top 10 Source code flaws for 2009</center>'''

Revision as of 11:00, 15 December 2008

The OWASP Source Code Flaws Top 10

C1 - XSS flaws occur whenever an application takes user supplied data and sends it to a web browser without first validating or encoding that content. XSS allows attackers to execute script in the victim's browser which can hijack user sessions, deface web sites, possibly introduce worms, etc.
C2 - Injection flaws, particularly SQL injection, are common in web applications. Injection occurs when user-supplied data is sent to an interpreter as part of a command or query. The attacker's hostile data tricks the interpreter into executing unintended commands or changing data.
C3 - Code vulnerable to remote file inclusion (RFI) allows attackers to include hostile code and data, resulting in devastating attacks, such as total server compromise. Malicious file execution attacks affect PHP, XML and any framework which accepts filenames or files from users.
C4 - A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, database record, or key, as a URL or form parameter. Attackers can manipulate those references to access other objects without authorization.
C5 - A CSRF attack forces a logged-on victim's browser to send a pre-authenticated request to a vulnerable web application, which then forces the victim's browser to perform a hostile action to the benefit of the attacker. CSRF can be as powerful as the web application that it attacks.
C6 - Applications can unintentionally leak information about their configuration, internal workings, or violate privacy through a variety of application problems. Attackers use this weakness to steal sensitive data, or conduct more serious attacks.
C7 - Account credentials and session tokens are often not properly protected. Attackers compromise passwords, keys, or authentication tokens to assume other users' identities.
C8 - Web applications rarely use cryptographic functions properly to protect data and credentials. Attackers use weakly protected data to conduct identity theft and other crimes, such as credit card fraud.
C9 - Applications frequently fail to encrypt network traffic when it is necessary to protect sensitive communications.
C10 - Frequently, an application only protects sensitive functionality by preventing the display of links or URLs to unauthorized users. Attackers can use this weakness to access and perform unauthorized operations by accessing those URLs directly.
Table 1: Top 10 Source code flaws for 2009

This category currently contains no pages or media.