Top 10 2004 - Revision history

Wichers: /* NOTE: THIS IS NOT THE CURRENT VERSION */

2013-07-03T21:16:50Z

‎NOTE: THIS IS NOT THE CURRENT VERSION

2013-07-03T21:16:22Z

2013-02-03T21:22:04Z

‎NOTE: THIS IS NOT THE CURRENT VERSION

2010-04-20T22:50:55Z

2008-10-10T12:21:48Z

Protected "Top 10 2004" [edit=sysop:move=sysop]

2008-10-09T14:39:40Z

2008-10-09T14:38:34Z

2008-10-09T14:37:32Z

2008-10-09T14:36:18Z

2008-10-09T14:01:36Z

@@ Line 1: / Line 1: @@
 =NOTE: THIS IS NOT THE CURRENT VERSION=
-Please visit the [[OWASP_Top_10]] project page to find the latest edition.
+Please visit the [[OWASP Top 10]] project page to find the latest edition.
 '''Welcome to the OWASP Top Ten 2004'''

@@ Line 1: / Line 1: @@
 =NOTE: THIS IS NOT THE CURRENT VERSION=
-Please visit the [[Top 10 2010]] to access the latest edition.
+Please visit the [[OWASP_Top_10]] project page to find the latest edition.
 '''Welcome to the OWASP Top Ten 2004'''
@@ Line 130: / Line 130: @@
 ==Project Sponsors==
-The OWASP Top Ten project is sponsored by
+The OWASP Top Ten project is sponsored by {{MemberLinks|link=http://www.aspectsecurity.com|logo=Aspect_logo_owasp.jpg}}
 [[Category:OWASP Project]]

@@ Line 1: / Line 1: @@
 =NOTE: THIS IS NOT THE CURRENT VERSION=
-Please visit the [[Top 10 2007]] to access the latest edition.
+Please visit the [[Top 10 2010]] to access the latest edition.
 '''Welcome to the OWASP Top Ten 2004'''

← Older revision		Revision as of 22:50, 20 April 2010
Line 136:		Line 136:
	[[Category:OWASP Document]]		[[Category:OWASP Document]]
	[[Category:OWASP Download]]		[[Category:OWASP Download]]
		+	[[Category:OWASP Top Ten Project]]

@@ Line 61: / Line 61: @@
 :Attackers can consume web application resources to a point where other legitimate users can no longer access or use the application. Attackers can also lock users out of their accounts or even cause the entire application to fail.
-;[[Insecure_Configuration_Management|A10 2004 Insecure Configuration Management]]
+;[[A10 2004 Insecure Configuration Management]]
 :Having a strong server configuration standard is critical to a secure web application. These servers have many configuration options that affect security and are not secure out of the box.

← Older revision	Revision as of 12:21, 10 October 2008
(No difference)

@@ Line 58: / Line 58: @@
 :Web applications frequently use cryptographic functions to protect information and credentials. These functions and the code to integrate them have proven difficult to code properly, frequently resulting in weak protection.
-;[[Application_Denial_of_Service|A9 2004 Application Denial of Service]]
+;[[A9 2004 Application Denial of Service]]
 :Attackers can consume web application resources to a point where other legitimate users can no longer access or use the application. Attackers can also lock users out of their accounts or even cause the entire application to fail.

@@ Line 55: / Line 55: @@
 :Error conditions that occur during normal operation are not handled properly. If an attacker can cause errors to occur that the web application does not handle, they can gain detailed system information, deny service, cause security mechanisms to fail, or crash the server.
-;[[Insecure_Storage|A8 2004 Insecure Storage]]
+;[[A8 2004 Insecure Storage]]
 :Web applications frequently use cryptographic functions to protect information and credentials. These functions and the code to integrate them have proven difficult to code properly, frequently resulting in weak protection.

@@ Line 52: / Line 52: @@
 :Web applications pass parameters when they access external systems or the local operating system. If an attacker can embed malicious commands in these parameters, the external system may execute those commands on behalf of the web application.
-;[[Improper_Error_Handling|A7 2004 Improper Error Handling]]
+;[[A7 2004 Improper Error Handling]]
 :Error conditions that occur during normal operation are not handled properly. If an attacker can cause errors to occur that the web application does not handle, they can gain detailed system information, deny service, cause security mechanisms to fail, or crash the server.

@@ Line 49: / Line 49: @@
 :Web application components in some languages that do not properly validate input can be crashed and, in some cases, used to take control of a process. These components can include CGI, libraries, drivers, and web application server components.
-;[[Injection_Flaws|A6 2004 Injection Flaws]]
+;[[A6 2004 Injection Flaws]]
 :Web applications pass parameters when they access external systems or the local operating system. If an attacker can embed malicious commands in these parameters, the external system may execute those commands on behalf of the web application.