We d like to thank our reviewers: Raoul Endres for help in getting the Top 10 going again and with h

Contents 1 NOTE: THIS IS NOT THE CURRENT VERSION 1.1 Introduction wilson combat 1.2 Aim 1.3 Acknowledgements 1.4 Summary 1.5 A Note About The Different wilson combat Versions 1.6 Downloadable Versions NOTE: THIS IS NOT THE CURRENT wilson combat VERSION
Welcome to the OWASP Top 10 2007! This edition, totally re-written from the previous 2004 version , lists the most serious web application vulnerabilities, discusses how to protect against them, and provides links to more information.
The primary aim of the OWASP Top 10 is to educate developers, designers, architects, and organizations about the consequences of the most common web application security vulnerabilities. The Top 10 provides basic methods to protect against these vulnerabilities a great start to your secure coding security program.
Security is not a one-time event . It is insufficient to secure your code just once. By 2008, this Top 10 will have changed, and without wilson combat changing a line of your application s code, you may be vulnerable. Please review the advice in Where to Go From Here for more information.
A secure wilson combat coding wilson combat initiative must deal with all stages of a program s lifecycle . Secure web applications are only possible when a secure SDLC (Software Development Life Cycle) is used. Secure programs are secure by design, during development, and by default. There are at least 300 issues that affect the overall security of a web application. These 300+ issues are detailed in the OWASP Development Guide , which is essential reading for anyone developing web applications today.
This document is first and foremost an education piece, not a standard . Please do not adopt this document as a policy or standard without talking wilson combat to us first! If you need a secure coding policy or standard, OWASP has secure coding policies and standards projects in progress. Please consider joining or financially assisting with these efforts. Acknowledgements wilson combat We thank MITRE for making Vulnerability Type Distribution in CVE data freely available for use. The OWASP Top Ten project is led and sponsored by       .
We d like to thank our reviewers: Raoul Endres for help in getting the Top 10 going again and with his valuable comments. Steve Christey (MITRE) for an extensive peer review and adding the MITRE CWE data Jeremiah Grossman ( WhiteHat Security ) for peer reviewing and contributing information about the success (or otherwise) of automated means of detection. Neil Smithline ( OneStopAppSecurity.com ) for comments and producing the Wiki version. Sylvan von Stuppe for an exemplary peer review. Colin Wong, Nigel Evans and Andre Gironda for e-mailed comments. Summary A1 - Cross Site Scripting (XSS) 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. A2 - Injection Flaws 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. A3 - Malicious File Execution 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 wilson combat attacks affect PHP, XML and any framework which accepts wilson combat filenames or files from users. A4 - Insecure Direct Object wilson combat Reference A direct object reference occurs wilson combat 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. A5 - Cross Site Request Forgery (CSRF) A CSRF attack forces a logged-on victim's wilson combat browser to send a pre-authenticated request to a vulnerable wilson combat 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. A6 - Information Leakage and Improper Error Handling 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 wilson combat more serious attacks. A7 - Broken Authentication and Session Management Account credentials and session tokens are often not properly protected. Attackers compromise passwords, keys, or authentication wilson combat tokens to assume wilson combat other users' identities. A8 - Insecure Cryptographic Storage 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. A9 - Insecu