Unsafe function call from a signal handler - Revision history

Jmanico at 21:39, 28 July 2016

2016-07-28T21:39:03Z

KirstenS: /* Related Controls */

2009-03-01T13:29:19Z

‎Related Controls

KirstenS at 02:02, 21 February 2009

2009-02-21T02:02:13Z

KirstenS at 14:22, 19 February 2009

2009-02-19T14:22:19Z

KirstenS: /* Related Vulnerabilities */

2009-02-18T00:21:04Z

‎Related Vulnerabilities

KirstenS at 14:18, 9 November 2008

2008-11-09T14:18:31Z

KirstenS at 13:22, 3 October 2008

2008-10-03T13:22:40Z

Weilin Zhong at 21:27, 4 August 2006

2006-08-04T21:27:08Z

Pravir Chandra at 04:05, 28 May 2006

2006-05-28T04:05:51Z

Deleted user at 18:37, 16 May 2006

2006-05-16T18:37:51Z

@@ Line 3: / Line 3: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==
@@ Line 52: / Line 50: @@
 See ''Race condition in signal handler'', for an example usage of free() in a signal handler which is exploitable.
 ==Related [[Controls]]==
@@ Line 70: / Line 56: @@
 * Design: Design signal handlers to only set flags rather than perform complex functionality.
 * Implementation: Ensure that non-reentrant functions are not found in signal handlers. Also, use sanity checks to ensure that state is consistently performing asynchronous actions which effect the state of execution.
 __NOTOC__
 [[Category:Vulnerability]]

@@ Line 67: / Line 67: @@
 ==Related [[Controls]]==
-* Requirements specification: A language might be chosen, which is not subject to this flaw, through a guarantee of reentrant code.
+* Requirements specification: A language might be chosen which is not subject to this flaw, through a guarantee of reentrant code.
 * Design: Design signal handlers to only set flags rather than perform complex functionality.
 * Implementation: Ensure that non-reentrant functions are not found in signal handlers. Also, use sanity checks to ensure that state is consistently performing asynchronous actions which effect the state of execution.
 ==Related [[Technical Impacts]]==

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:SecureSoftware}}
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:SecureSoftware}}
+<br>
 [[ASDR Table of Contents]]
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==
 There are several functions which - under certain circumstances, if used in a signal handler - may result in the corruption of memory, allowing for exploitation of the process.

@@ Line 68: / Line 68: @@
 ==Related [[Vulnerabilities]]==
-* [[Race condition in signal handler]]
+* [[Race conditions]]
 * [[Write-what-where condition]]
 ==Related [[Controls]]==

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:SecureSoftware}}
-==Overview==
+[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
-There are several functions which - under certain circumstances, if used in a signal handler - may result in the corruption of memory, allowing for exploitation of the process.
+[[ASDR Table of Contents]]
-*	Access control: It may be possible to execute arbitrary code through the use of a write-what-where condition.
+==Description==
-*	Integrity: Signal race conditions often result in data corruption.
+There are several functions which - under certain circumstances, if used in a signal handler - may result in the corruption of memory, allowing for exploitation of the process.
-==Exposure period ==
+'''Consequences'''
-*	Requirements specification: A language might be chosen which is not subject to this flaw.
+* Access control: It may be possible to execute arbitrary code through the use of a write-what-where condition.
-*	Design: Signal handlers with complicated functionality may result in this issue.
+'''Exposure period'''
-*	Implementation: The use of any number of non-reentrant functions will result in this issue.
+* Requirements specification: A language might be chosen which is not subject to this flaw.
-==Platform ==
+'''Platform'''
-*	Languages: C, C++, Assembly
+* Languages: C, C++, Assembly
-*	Platforms: All
+'''Required resources'''
 Any
-==Severity ==
+'''Severity'''
 High
-==Likelihood   of exploit ==
+'''Likelihood of exploit'''
 Low
-==Avoidance and mitigation ==
+This flaw is a subset of race conditions occurring in signal handler calls which is concerned primarily with memory corruption caused by calls to non-reentrant functions in signal handlers.
-*	Requirements specification: A language might be chosen, which is not subject to this flaw, through a guarantee of reentrant code.
+* [[Race condition in signal handler]]
-==Discussion ==
+==Related [[Controls]]==
-This flaw is a subset of race conditions occurring in signal handler calls which is concerned primarily with memory corruption caused by calls to non-reentrant functions in signal handlers.
+* Requirements specification: A language might be chosen, which is not subject to this flaw, through a guarantee of reentrant code.
-Non-reentrant functions are functions that cannot safely be called, interrupted, and then recalled before the first call has finished without resulting in memory corruption. The function call syslog() is an example of this. In order to perform its functionality, it allocates a small amount of memory as "scratch space." If syslog() is suspended by a signal call and the signal handler calls syslog(), the memory used by both of these functions enters an undefined, and possibly, exploitable state.
+Encoding Vulnerability
-==Examples ==
+Error Handling Vulnerability
-See ''Race condition in signal handler'', for an example usage of free() in a signal handler which is exploitable.
+Input Validation Vulnerability
-==Related problems ==
+Logging and Auditing Vulnerability
-*	[[Race condition in signal handler]]
+Session Management Vulnerability]]
-*	[[Write-what-where condition]]
+__NOTOC__
 [[Category:Use of Dangerous API]]
 [[Category:Synchronization and Timing Vulnerability]]
 [[Category:OWASP_CLASP_Project]]

← Older revision		Revision as of 18:37, 16 May 2006
Line 1:		Line 1:
−

	{{Template:SecureSoftware}}		{{Template:SecureSoftware}}
Line 68:		Line 67:

	[[Category:Synchronization and Timing Errror]]		[[Category:Synchronization and Timing Errror]]
		+
		+	[[Category:OWASP_CLASP_Project]]