Difference between revisions of "Missing Error Handling"

From OWASP
Jump to: navigation, search
Line 2: Line 2:
  
 
==Description==
 
==Description==
 +
 +
The application doesn't configure a defult generic error page for standard HTTP error codes, such as 404, 500 and java.lang.Throwable exceptions. The containers built-in error response will be returned. These error pages can provide clues to attackers, such as the requested file doesn't exist, or contain detailed information about the application, such as technologies used and their versions.
  
 
==Examples ==
 
==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.
  
 
==Related Threats==
 
==Related Threats==
Line 23: Line 26:
 
[[Category:Deployment]]
 
[[Category:Deployment]]
  
[[Category:Environmental Problem]]
+
[[Category:Environmental Vulnerability]]
  
 
[[Category:Error Handling Vulnerability]]
 
[[Category:Error Handling Vulnerability]]

Revision as of 13:48, 29 June 2006

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Description

The application doesn't configure a defult generic error page for standard HTTP error codes, such as 404, 500 and java.lang.Throwable exceptions. The containers built-in error response will be returned. These error pages can provide clues to attackers, such as the requested file doesn't exist, or contain detailed information about the application, such as technologies used and their versions.

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.

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

Category:Error Handling

Categories

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.