Difference between revisions of "Often Misused: Exception Handling"

From OWASP
Jump to: navigation, search
Line 2: Line 2:
 
{{Template:Fortify}}
 
{{Template:Fortify}}
  
 
+
__TOC__
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
+
 
+
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
+
  
 
[[ASDR Table of Contents]]
 
[[ASDR Table of Contents]]
__TOC__
 
  
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
==Description==
 
==Description==
Line 67: Line 64:
 
[[Category:Implementation]]
 
[[Category:Implementation]]
 
[[Category:API Abuse]]
 
[[Category:API Abuse]]
 +
[[Category:Vulnerability]]

Revision as of 08:46, 4 November 2008

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


This article includes content generously donated to OWASP by Fortify.JPG.

Contents


ASDR Table of Contents

Last revision (mm/dd/yy): 11/4/2008

Description

The _alloca() function can throw a stack overflow exception, potentially causing the program to crash.

Description

The _alloca() function allocates memory on the stack. If an allocation request is too large for the available stack space, _alloca() throws an exception. If the exception is not caught, the program will crash, potentially enabling a denial of service attack.

_alloca() has been deprecated as of Microsoft Visual Studio 2005®. It has been replaced with the more secure _alloca_s().


Risk Factors

TBD

Examples

Short example name

TBD

Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

TBD