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: Misspelled Method Name"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
{{Template:Vulnerability}}
+
{{template:CandidateForDeletion}}
{{Template:Fortify}}
+
 
 +
#REDIRECT [[Failure to follow guideline/specification]]
  
 
__TOC__
 
__TOC__
Line 58: Line 59:
 
==References==
 
==References==
 
TBD
 
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:Code Quality Vulnerability]]
 
[[Category:Java]]
 
[[Category:Implementation]]
 
[[Category:Code Snippet]]
 
[[Category:Vulnerability]]
 

Revision as of 11:25, 11 February 2009

Template:CandidateForDeletion

#REDIRECT Failure to follow guideline/specification

ASDR Table of Contents

Last revision (mm/dd/yy): 02/11/2009


Description

This looks like an effort to override a common Java method, but it probably does not have the intended effect.

This method's name is similar to a common Java method name, but it is either spelled incorrectly or the argument list causes it to not override the intended method.

Risk Factors

TBD

Examples

The following method is meant to override Object.equals():

	public boolean equals(Object obj1, Object obj2) {
	  ...
	}

But since Object.equals() only takes a single argument, the method above is never called.

Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References

TBD