Top 10 2007

Introduction
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 OWASP Top 10 has been translated into French. Click Here for the French Translation!'''

The OWASP Top 10 for Java Enterprise Edition is available for download here

Aim
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 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 coding 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 [mailto:owasp@owasp.org talking 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
Project Lead: 	Andrew van der Stock (Executive Director, OWASP Foundation)

Co-authors: 	Jeff Williams (Chair, OWASP Foundation), Dave Wichers (Conference Chair, OWASP Foundation)

We’d like to thank our reviewers:


 * Raoul Endres for help in getting the Top 10 going again and with his valuable comments.
 * [mailto:coley...at...mitre.org 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
 Table 1: Top 10 Web application vulnerabilities for 2007 

There are several pages in this document that are not dedicated to a specific vulnerability and hence are not listed in the table. Here is the list of them.

' Table 1a: Pages in the OWASP Top Ten 2007'' document other than the vulnerability pages listed above. '''

A Note About The Different Versions
While the only official version of the OWASP Top Ten 2007 list is the downloadable English PDF version, OWASP has put together this Wiki that initially contains the same content as the PDF. But OWASP hopes that will change with your help. OWASP encourages community involvement and wants your help to make the Wiki version even better. To aid in this they have put together a brief tutorial to get you started.

Downloadable Versions
You can download the Top 10 2007 (Final) here:


 * (PDF, 930 kb)


 * (French Version PDF, 455 kb)


 * (Korean Version PDF, 768 kb)


 * (Turkish Version PDF, 718 kb)


 * (Brazilian Portuguese PDF, 329 kb)


 * (Spanish PDF, 488kb)


 * OWASP Top 10 for Java Enterprise Edition (PDF, 630 kb)


 * Looking for a version in another language? We could use your help translating. Contact Andrew van der Stock (vanderaj ...(@)... owasp.org) to help translating the OWASP Top 10 into your language.