This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Return Inside Finally Block"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 
{{Template:Fortify}}
 
{{Template:Fortify}}
<br>
 
[[ASDR Table of Contents]]
 
  
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
  
  
Line 12: Line 11:
  
 
A return statement inside a finally block will cause any exception that might be thrown in the try block to be discarded.
 
A return statement inside a finally block will cause any exception that might be thrown in the try block to be discarded.
 
  
  

Revision as of 15:42, 28 February 2009

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

This article includes content generously donated to OWASP by MicroFocus Logo.png

Last revision (mm/dd/yy): 02/28/2009

Vulnerabilities Table of Contents


Description

Returning from inside a finally block will cause exceptions to be lost.

A return statement inside a finally block will cause any exception that might be thrown in the try block to be discarded.


Risk Factors

TBD

Examples

In the following code excerpt, the IllegalArgumentException will never be delivered to the caller. The finally block will cause the exception to be discarded.

	try {
	  ...
	  throw IllegalArgumentException();
	}
	finally {
	  return r;
	}


Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

Note: A reference to related CWE or CAPEC article should be added when exists. Eg: