Difference between revisions of "Often Misused: Exception Handling"

From OWASP
Jump to: navigation, search
 
Line 1: Line 1:
 +
{{Template:Fortify}}
 +
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 +
 +
==Abstract==
 +
 +
The _alloca() function can throw a stack overflow exception, potentially causing the program to crash.
  
 
==Description==
 
==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().
  
 
==Examples ==
 
==Examples ==
Line 18: Line 28:
  
 
[[Category:Error Handling Vulnerability]]
 
[[Category:Error Handling Vulnerability]]
 +
 +
[[Category:API Abuse]]
 +
 +
[[Category:C]]
 +
 +
[[Category:Implementation]]

Revision as of 09:53, 18 July 2006

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

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


Abstract

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().

Examples

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

Categories

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