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
| Line 3: | Line 3: | ||
#REDIRECT [[Failure to follow guideline/specification]] | #REDIRECT [[Failure to follow guideline/specification]] | ||
| − | |||
| − | |||
| − | |||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
Latest revision as of 23:31, 7 April 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 04/7/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
