Missing Error Handling - Revision history

Imifos: Moved page into the right category. See Java space page for me details. Content has not been reviewed in this edit.

2017-11-10T11:48:04Z

Moved page into the right category. See Java space page for me details. Content has not been reviewed in this edit.

2015-12-01T13:07:37Z

2009-02-26T18:34:42Z

‎Examples

2009-02-26T18:34:23Z

‎Description

2009-02-26T14:58:10Z

2009-02-26T14:56:16Z

‎Description

2009-02-21T01:39:32Z

2009-02-18T02:42:41Z

2009-02-17T16:46:20Z

2008-11-02T20:43:22Z

@@ Line 54: / Line 54: @@
 [[Category:OWASP ASDR Project]]
-[[Category:OWASP Java Project]]
+[[Category:Java]]
 [[Category:Deployment]]
 [[Category:Environmental Vulnerability]]
 [[Category:Error Handling Vulnerability]]
 [[Category:Vulnerability]]

@@ Line 54: / Line 54: @@
 [[Category:OWASP ASDR Project]]
-[[Category:Java]]
+[[Category:OWASP Java Project]]
 [[Category:Deployment]]
 [[Category:Environmental Vulnerability]]
 [[Category:Error Handling Vulnerability]]
 [[Category:Vulnerability]]

@@ Line 20: / Line 20: @@
 ==Examples==
-A "HTTP 404 - File not found" error tells an attacker that the requested file doesn't exist rather than that he doesn't have access to the file. This can help attacker to decide his next step.
+An "HTTP 404 - File not found" error tells an attacker that the requested file doesn't exist rather than that he doesn't have access to the file. This can help the attacker to decide his next step.
 ==Related [[Attacks]]==

@@ Line 8: / Line 8: @@
 ==Description==
-A web application must define a default error page for 404 errors, 500 errors and to catch java.lang. Throwable exceptions to prevent attackers from mining information from the application container's built-in error response.
+A web application must define a default error page for 404 errors, 500 errors, and to catch java.lang. Throwable exceptions prevent attackers from mining information from the application container's built-in error response.
 When an attacker explores a web site looking for vulnerabilities, the amount of information that the site provides is crucial to the eventual success or failure of any attempted attacks. If the application shows the attacker a stack trace, it relinquishes information that makes the attacker's job significantly easier. For example, a stack trace might show the attacker a malformed SQL query string, the type of database being used, and the version of the application container. This information enables the attacker to target known vulnerabilities in these components.

← Older revision		Revision as of 14:58, 26 February 2009
Line 50:		Line 50:
	TBD		TBD

−	~~[[Category:FIXME\|add links~~

−	~~In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>~~
−
−	~~Availability Vulnerability~~
−
−	~~Authorization Vulnerability~~
−
−	~~Authentication Vulnerability~~
−
−	~~Concurrency Vulnerability~~
−
−	~~Configuration Vulnerability~~
−
−	~~Cryptographic Vulnerability~~
−
−	~~Encoding Vulnerability~~
−
−	~~Error Handling Vulnerability~~
−
−	~~Input Validation Vulnerability~~
−
−	~~Logging and Auditing Vulnerability~~
−
−	~~Session Management Vulnerability]]~~

	__NOTOC__		__NOTOC__

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:Fortify}}
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 ==Description==

← Older revision	Revision as of 16:46, 17 February 2009
(No difference)