Difference between revisions of "Top 10 2013-Top 10"

From OWASP
Jump to: navigation, search
m (deleted a <cr>)
 
(11 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
     |next=A1-{{Top_10_2010:ByTheNumbers
 
     |next=A1-{{Top_10_2010:ByTheNumbers
 
               |1
 
               |1
               |year=2013}}
+
               |year=2013
 +
              |language=en
 +
          }}
 
     |useprev=2013PrevLink
 
     |useprev=2013PrevLink
     |prev=Risk
+
     |prev={{Top_10:LanguageFile|text=risk|year=2013|language=en}}
 +
    |year=2013
 +
    |language=en
 
}}
 
}}
  
 
{| cellspacing="1" cellpadding="1" border="0" width="100%;"
 
{| cellspacing="1" cellpadding="1" border="0" width="100%;"
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A1-Injection
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=1|language=en}}<br/>A1-{{Top_10_2010:ByTheNumbers|1|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
    {{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing unauthorized data.
+
Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A2–Broken Authentication and Session Management
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=2|language=en}}<br/>A2-{{Top_10_2010:ByTheNumbers|2|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, session tokens, or  exploit other implementation flaws to assume other users’ identities.
+
Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or  to exploit other implementation flaws to assume other users’ identities.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A3–Cross-Site Scripting (XSS)
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=3|language=en}}<br/>A3-{{Top_10_2010:ByTheNumbers|3|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
 
XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
 +
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A4–Insecure Direct Object References
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=4|language=en}}<br/>A4-{{Top_10_2010:ByTheNumbers|4|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.
 
A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.
 +
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A5–Security Misconfiguration
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=5|language=en}}<br/>A5-{{Top_10_2010:ByTheNumbers|5|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. All these settings should be defined, implemented, and maintained as many are not shipped with secure defaults. This includes keeping all software up to date.
+
Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A6–Sensitive Data Exposure
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=6|language=en}}<br/>A6-{{Top_10_2010:ByTheNumbers|6|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Many web applications do not properly protect sensitive data, such as credit cards, tax ids, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct identity theft, credit card fraud, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
+
Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A7–Missing Function Level Access Control
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=7|language=en}}<br/>A7-{{Top_10_2010:ByTheNumbers|7|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Virtually all web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access unauthorized functionality.
+
Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A8-Cross-Site Request Forgery (CSRF)
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=8|language=en}}<br/>A8-{{Top_10_2010:ByTheNumbers|8|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
 
A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
 +
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A9-Using Components with Known Vulnerabilities
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=9|language=en}}<br/>A9-{{Top_10_2010:ByTheNumbers|9|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
Vulnerable components, such as libraries, frameworks, and other software modules almost always run with full privilege. So, if exploited, they can cause serious data loss or server takeover. Applications using these vulnerable components may undermine their defenses and enable a range of possible attacks and impacts.
+
Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If  a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.
 +
 
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A10–Unvalidated Redirects and Forwards
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=10|language=en}}<br/>A10-{{Top_10_2010:ByTheNumbers|10|year=2013|language=en}}
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
|{{Top 10:GrayBoxBegin|year=2013}}
 
Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.  
 
Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.  
 +
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|}
 
|}
Line 75: Line 89:
 
     |next=A1-{{Top_10_2010:ByTheNumbers
 
     |next=A1-{{Top_10_2010:ByTheNumbers
 
               |1
 
               |1
               |year=2013}}
+
               |year=2013
 +
              |language=en
 +
          }}
 
     |useprev=2013PrevLink
 
     |useprev=2013PrevLink
     |prev=Risk
+
     |prev={{Top_10:LanguageFile|text=risk|year=2013|language=en}}
 +
    |year=2013
 +
    |language=en
 
}}
 
}}
 
[[Category:OWASP Top Ten Project]]
 
[[Category:OWASP Top Ten Project]]
 

Latest revision as of 15:47, 23 June 2013

← Risk
2013 Table of Contents

2013 Top 10 List

A1-Injection →

A1-Injection

Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.


A2-Broken Authentication and Session Management

Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.


A3-Cross-Site Scripting (XSS)

XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.


A4-Insecure Direct Object References

A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to access unauthorized data.


A5-Security Misconfiguration

Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.


A6-Sensitive Data Exposure

Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.


A7-Missing Function Level Access Control

Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.


A8-Cross-Site Request Forgery (CSRF)

A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.


A9-Using Components with Known Vulnerabilities

Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.


A10-Unvalidated Redirects and Forwards

Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.


← Risk
2013 Table of Contents

2013 Top 10 List

A1-Injection →

© 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