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

From OWASP
Jump to: navigation, search
(17 intermediate revisions by one user not shown)
Line 1: Line 1:
 
+
{{Top_10_2013:TopTemplate
 +
    |usenext=2013NextLink
 +
    |next={{Top_10_2010:ByTheNumbers
 +
              |1
 +
              |year=2013}}
 +
    |useprev=2013PrevLink
 +
    |prev=Risk
 +
}}
  
 
{| cellspacing="1" cellpadding="1" border="0" width="100%;"
 
{| cellspacing="1" cellpadding="1" border="0" width="100%;"
|{{Top 10:RoundedBoxBegin|year=2013}}A1-Injection{{Top 10:RoundedBoxEnd|year=2013}}
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=1}}<br/>A1-Injection
|{{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.{{Top 10:GrayBoxEnd|year=2013}}
+
    {{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|{{Top 10:RoundedBoxBegin|year=2013}}A2-Broken Authentication and Session Management
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=2}}A2–Broken Authentication and Session Management
{{Top 10:RoundedBoxEnd|year=2013}}
+
{{Top 10:RoundedBoxLinkEnd|year=2013}}
|XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation and 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: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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A3|A3-Broken Authentication and Session Management]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=3}}<br/>A3–Cross-Site Scripting (XSS)
|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.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A4|A4-Insecure Direct Object References]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=4}}<br/>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.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A5|A5-Cross Site Request Forgery (CSRF)]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=6}}<br/>A5–Security Misconfiguration
|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:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A6|A6-Security Misconfiguration]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=6}}<br/>A6–Sensitive Data Exposure
|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, including all code libraries used by the application.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A7|A7-Insecure Cryptographic Storage]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=7}}A7–Missing Function Level Access Control
|Many web applications do not properly protect sensitive data, such as credit cards, SSNs, and authentication credentials, with appropriate encryption or hashing. Attackers may steal or modify such weakly protected data to conduct identity theft, credit card fraud, or other crimes.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A8|A8-Failure to Restrict URL Access]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=8}}A8-Cross-Site Request Forgery (CSRF)
|Many web applications check URL access rights before rendering protected links and buttons. However, applications need to perform similar access control checks each time these pages are accessed, or attackers will be able to forge URLs to access these hidden pages anyway.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A9|A9-Insufficient Transport Layer Protection]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=9}}A9-Using Components with Known Vulnerabilities
|Applications frequently fail to authenticate, encrypt, and protect the confidentiality and integrity of sensitive network traffic. When they do, they sometimes support weak algorithms, use expired or invalid certificates, or do not use them correctly.
+
{{Top 10:RoundedBoxLinkEnd|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.
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|-
 
|-
|<center>[[Top_10_2010-A10|A10-Unvalidated Redirects and Forwards]]</center>
+
|{{Top 10:RoundedBoxLinkBegin|year=2013|risk=10}}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.
+
{{Top 10:RoundedBoxLinkEnd|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.  
 +
{{Top 10:GrayBoxEnd|year=2013}}
 
|}
 
|}
 +
 +
{{Top_10_2013:BottomTemplate
 +
    |type={{Top_10_2010:StyleTemplate}}
 +
    |usenext=2013NextLink
 +
    |next={{Top_10_2010:ByTheNumbers
 +
              |1
 +
              |year=2013}}
 +
    |useprev=2013PrevLink
 +
    |prev=Risk
 +
}}

Revision as of 22:30, 8 March 2013

[[Top 10 {{{year}}}-Risk|← Risk]]
2013 Table of Contents

2013 Top 10 List

[[Top 10 {{{year}}}-Injection|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 unauthorized data.

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, session tokens, or 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. 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.


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 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.

A7–Missing Function Level Access Control

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.

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

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.

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.


[[Top 10 {{{year}}}-Risk|← Risk]]
2013 Table of Contents

2013 Top 10 List

[[Top 10 {{{year}}}-Injection|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
[[Category:OWASP Top Ten {{{year}}} Project]]