Using the wrong operator - Revision history

Jmanico: Redirected page to Vulnerabilities

2014-04-05T19:03:59Z

Redirected page to Vulnerabilities

KirstenS: /* Related Controls */

2009-03-01T14:00:30Z

‎Related Controls

KirstenS: /* Description */

2009-03-01T13:59:56Z

‎Description

KirstenS at 02:07, 21 February 2009

2009-02-21T02:07:43Z

KirstenS at 14:28, 19 February 2009

2009-02-19T14:28:51Z

KirstenS at 17:36, 9 November 2008

2008-11-09T17:36:46Z

KirstenS at 16:00, 3 October 2008

2008-10-03T16:00:38Z

Weilin Zhong at 18:33, 26 June 2006

2006-06-26T18:33:26Z

Pravir Chandra at 04:04, 28 May 2006

2006-05-28T04:04:55Z

Deleted user at 18:39, 16 May 2006

2006-05-16T18:39:33Z

← Older revision		Revision as of 19:03, 5 April 2014
Line 1:		Line 1:
−	~~{{Template:Vulnerability}}~~	+	#REDIRECT [[Vulnerabilities]]
−	~~{{Template:SecureSoftware}}~~
−
−	~~Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''~~
−
−	[[~~ASDR_TOC_Vulnerabilities\|~~Vulnerabilities ~~Table of Contents]]~~
−
−	~~==Description==~~
−	~~This is a common error given when an operator is used which does not make sense in context.~~
−
−	~~'''Consequences'''~~
−
−	~~Unspecified.~~
−
−	~~'''Exposure period'''~~
−
−	* Pre-design through Build: The use of tools to detect this problem is recommended.
−	* Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack, of or misuse, of mitigating technologies.
−
−	~~'''Platform'''~~
−
−	* Languages: Any
−	* Operating platforms: Any
−
−	~~'''Required resources'''~~
−
−	~~Any~~
−
−	~~'''Severity'''~~
−
−	~~Medium~~
−
−	~~'''Likelihood of exploit'''~~
−
−	~~Low~~
−
−	These types of bugs generally are the result of a typo. Although most of them can easily be found when testing of the program, it is important that one correct these problems, since they almost certainly will break the code.
−
−	~~==Risk Factors==~~
−
−	~~TBD~~
−
−
−	~~==Examples==~~
−
−	~~In C:~~
−
−	~~<pre>~~
−	~~char foo;~~
−	~~foo=a+c;~~
−	~~</pre>~~
−
−
−	~~==Related [[Attacks]]==~~
−
−	* [[Attack 1]]
−	* [[Attack 2]]
−
−
−	~~==Related [[Vulnerabilities]]==~~
−
−	* [[Vulnerability 1]]
−	* [[Vulnerabiltiy 2]]
−
−
−
−	~~==Related [[Controls]]==~~
−
−	* Pre-design through Build: Most static analysis programs should be able to catch these errors.
−	* Implementation: Save an index variable. This is the recommended solution. Rather than subtract pointers from one another, use an index variable of the same size as the pointers in question. Using this variable, "walk" from one pointer to the other and calculate the difference. Always sanity check this number.
−
−	~~==Related [[Technical Impacts]]==~~
−
−	* [[Technical Impact 1]]
−	* [[Technical Impact 2]]
−
−
−	~~==References==~~
−
−	~~TBD~~
−	~~[[Category:FIXME\|add links~~
−
−	~~In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>~~
−
−	~~Availability Vulnerability~~
−
−	~~Authorization Vulnerability~~
−
−	~~Authentication Vulnerability~~
−
−	~~Concurrency Vulnerability~~
−
−	~~Configuration Vulnerability~~
−
−	~~Cryptographic Vulnerability~~
−
−	~~Encoding Vulnerability~~
−
−	~~Error Handling Vulnerability~~
−
−	~~Input Validation Vulnerability~~
−
−	~~Logging and Auditing Vulnerability~~
−
−	~~Session Management Vulnerability]]~~
−
−	~~__NOTOC__~~
−
−
−	~~[[Category:OWASP ASDR Project]]~~
−	~~[[Category:Vulnerability]]~~
−	~~[[Category:General Logic Error Vulnerability]]~~
−	~~[[Category:OWASP_CLASP_Project~~]]

@@ Line 68: / Line 68: @@
 * Pre-design through Build: Most static analysis programs should be able to catch these errors.
-* Implementation: Save an index variable. This is the recommended solution. Rather than subtract pointers from one another, use an index variable of the same size as the pointers in question. Use this variable "walk" from one pointer to the other and calculate the difference. Always sanity check this number.
+* Implementation: Save an index variable. This is the recommended solution. Rather than subtract pointers from one another, use an index variable of the same size as the pointers in question. Using this variable, "walk" from one pointer to the other and calculate the difference. Always sanity check this number.
 ==Related [[Technical Impacts]]==

@@ Line 7: / Line 7: @@
 ==Description==
-This is a common error given when an operator is used which does not make sense for the context appears.
+This is a common error given when an operator is used which does not make sense in context.
 '''Consequences'''
@@ Line 36: / Line 36: @@
 These types of bugs generally are the result of a typo. Although most of them can easily be found when testing of the program, it is important that one correct these problems, since they almost certainly will break the code.
 ==Risk Factors==

@@ 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==
 This is a common error given when an operator is used which does not make sense for the context appears.

@@ Line 1: / Line 1: @@
 {{Template:SecureSoftware}}
-==Overview==
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 This is a common error given when an operator is used which does not make sense for the context appears.
-==Consequences ==
+'''Consequences'''
 Unspecified.
-==Exposure period ==
+'''Exposure period'''
-*	Implementation: Many logic errors can lead to this condition. It can be exacerbated by lack, of or misuse, of mitigating technologies.
+* Pre-design through Build: The use of tools to detect this problem is recommended.
-==Platform ==
+'''Platform'''
-*	Languages: Any
+* Languages: Any
-*	Operating platforms: Any
+'''Required resources'''
 Any
-==Severity ==
+'''Severity'''
 Medium
-==Likelihood   of exploit ==
+'''Likelihood of exploit'''
 Low
-==Avoidance and mitigation ==
+These types of bugs generally are the result of a typo. Although most of them can easily be found when testing of the program, it is important that one correct these problems, since they almost certainly will break the code.
-==Discussion ==
+==Risk Factors==
-==Examples ==
+==Examples==
 In C:
@@ Line 52: / Line 60: @@
 </pre>
-Not available.
+==Related [[Attacks]]==
 [[Category:Vulnerability]]
 [[Category:General Logic Error Vulnerability]]
 [[Category:OWASP_CLASP_Project]]

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

	{{Template:SecureSoftware}}		{{Template:SecureSoftware}}
Line 63:		Line 62:

	[[Category:General Logic Errors]]		[[Category:General Logic Errors]]
		+
		+	[[Category:OWASP_CLASP_Project]]