Use of Obsolete Methods - Revision history

Imifos at 12:44, 22 January 2016

2016-01-22T12:44:55Z

Imifos at 12:48, 2 December 2015

2015-12-02T12:48:23Z

Jmanico at 18:38, 5 April 2014

2014-04-05T18:38:38Z

KirstenS at 02:04, 21 February 2009

2009-02-21T02:04:41Z

KirstenS at 14:23, 19 February 2009

2009-02-19T14:23:38Z

KirstenS at 17:24, 9 November 2008

2008-11-09T17:24:26Z

KirstenS at 14:09, 3 October 2008

2008-10-03T14:09:28Z

Jeff Williams: Obsolete moved to Use of Obsolete Methods: non-descriptive name

2006-08-29T20:35:57Z

Obsolete moved to Use of Obsolete Methods: non-descriptive name

Johncoswell: /* Description */

2006-08-29T14:51:09Z

‎Description

Weilin Zhong at 18:16, 20 July 2006

2006-07-20T18:16:32Z

@@ Line 38: / Line 38: @@
 [[Category:Code Quality Vulnerability]]
-[[Category:OWASP C/C++ Project]]
+[[Category:C/C++]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]
 [[Category:Use of Dangerous API]]
 [[Category:Vulnerability]]

@@ Line 38: / Line 38: @@
 [[Category:Code Quality Vulnerability]]
-[[Category:C]]
+[[Category:OWASP C/C++ Project]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]
 [[Category:Use of Dangerous API]]
 [[Category:Vulnerability]]

@@ Line 1: / Line 1: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
+= Description =
 The use of deprecated or obsolete functions may indicate neglected code.
@@ Line 18: / Line 13: @@
 Refer to the documentation for this function in order to determine why it is deprecated or obsolete and to learn about alternative ways to achieve the same functionality. The remainder of this text discusses general problems that stem from the use of deprecated or obsolete functions.
 = Risk Factors =
 * Talk about the [[OWASP Risk Rating Methodology|factors]] that make this vulnerability likely or unlikely to actually happen
@@ Line 25: / Line 19: @@
 * Consider the likely [business impacts] of a successful attack
 = Examples =
 The following code uses the deprecated function getpw() to verify that a plaintext password matches a user's encrypted password. If the password is valid, the function sets result to 1; otherwise it is set to 0.
@@ Line 44: / Line 37: @@
 Not all functions are deprecated or replaced because they pose a security risk. However, the presence of an obsolete function often indicates that the surrounding code has been neglected and may be in a state of disrepair. Software security has not been a priority, or even a consideration, for very long. If the program uses deprecated or obsolete functions, it raises the probability that there are security problems lurking nearby.
 [[Category:Code Quality Vulnerability]]
 [[Category:C]]

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

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
 {{Template:Fortify}}
+<br>
 [[ASDR Table of Contents]]
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 ==Description==
 The use of deprecated or obsolete functions may indicate neglected code.

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-==Abstract==
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 ==Description==
 As programming languages evolve, functions occasionally become obsolete due to:
@@ Line 17: / Line 25: @@
 Refer to the documentation for this function in order to determine why it is deprecated or obsolete and to learn about alternative ways to achieve the same functionality. The remainder of this text discusses general problems that stem from the use of deprecated or obsolete functions.
 ==Examples ==
 The following code uses the deprecated function getpw() to verify that a plaintext password matches a user's encrypted password. If the password is valid, the function sets result to 1; otherwise it is set to 0.
@@ Line 35: / Line 51: @@
 Not all functions are deprecated or replaced because they pose a security risk. However, the presence of an obsolete function often indicates that the surrounding code has been neglected and may be in a state of disrepair. Software security has not been a priority, or even a consideration, for very long. If the program uses deprecated or obsolete functions, it raises the probability that there are security problems lurking nearby.
-==Related Attacks==
+==Related [[Attacks]]==
-==Related Vulnerabilities==
+==Related [[Controls]]==
-==Related Countermeasures==
+* [[Control 1]]
 [[Category:Code Quality Vulnerability]]
 [[Category:C]]
 [[Category:Implementation]]
 [[Category:Code Snippet]]
 [[Category:Use of Dangerous API]]

← Older revision	Revision as of 20:35, 29 August 2006
(No difference)

@@ Line 10: / Line 10: @@
 As programming languages evolve, functions occasionally become obsolete due to:
-Advances in the language
+* Advances in the language
-Improved understanding of how operations should be performed effectively and securely
+* Improved understanding of how operations should be performed effectively and securely
-Changes in the conventions that govern certain operations
+* Changes in the conventions that govern certain operations
-Functions that are removed are usually replaced by newer counterparts that perform the same task in some different and hopefully improved way.
+* Functions that are removed are usually replaced by newer counterparts that perform the same task in some different and hopefully improved way.
 Refer to the documentation for this function in order to determine why it is deprecated or obsolete and to learn about alternative ways to achieve the same functionality. The remainder of this text discusses general problems that stem from the use of deprecated or obsolete functions.