This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Code Correctness: Erroneous finalize() Method"
From OWASP
Weilin Zhong (talk | contribs) |
(Reverting to last version not containing links to www.textpasricletoli.com) |
||
| (13 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | + | #REDIRECT [[Failure to follow guideline/specification]] | |
| − | |||
| − | + | ||
| + | |||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| + | |||
==Description== | ==Description== | ||
| + | |||
| + | This finalize() method does not call super.finalize(). | ||
The Java Language Specification states that it is a good practice for a finalize() method to call super.finalize().[1] | The Java Language Specification states that it is a good practice for a finalize() method to call super.finalize().[1] | ||
| + | <br>The statement above is not completely correct. The Java Language Specification 3.0 section 12.6.1 states: "This should | ||
| + | always be done, <b>unless it is the programmer's intent to nullify the actions of the finalizer in the superclass.</b>" | ||
| + | |||
| + | ==Risk Factors== | ||
| + | TBD | ||
==Examples == | ==Examples == | ||
| Line 19: | Line 28: | ||
} | } | ||
| − | ==Related | + | ==Related [[Attacks]]== |
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| − | |||
| − | [[ | + | ==Related [[Vulnerabilities]]== |
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| − | |||
| − | ==Related | + | ==Related [[Controls]]== |
| + | * [[Control 1]] | ||
| + | * [[Control 2]] | ||
| − | == | + | ==Related [[Technical Impacts]]== |
| + | * [[Technical Impact 1]] | ||
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | + | ==References== | |
| − | + | * [1] J. Gosling, B. Joy, G. Steele, G. Bracha. The Java Language Specification, Second Edition. Addison-Wesley, 2000. | |
| − | [ | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 18:27, 27 May 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 05/27/2009
[hide]
Description
This finalize() method does not call super.finalize().
The Java Language Specification states that it is a good practice for a finalize() method to call super.finalize().[1]
The statement above is not completely correct. The Java Language Specification 3.0 section 12.6.1 states: "This should
always be done, unless it is the programmer's intent to nullify the actions of the finalizer in the superclass."
Risk Factors
TBD
Examples
The following method omits the call to super.finalize().
protected void finalize() {
discardNative();
}
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
- [1] J. Gosling, B. Joy, G. Steele, G. Bracha. The Java Language Specification, Second Edition. Addison-Wesley, 2000.
