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 1: | Line 1: | ||
{{Template:Vulnerability}} | {{Template:Vulnerability}} | ||
{{Template:Fortify}} | {{Template:Fortify}} | ||
| − | |||
| − | + | __TOC__ | |
[[ASDR Table of Contents]] | [[ASDR Table of Contents]] | ||
| − | + | ||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| Line 93: | Line 93: | ||
[[Category:Implementation]] | [[Category:Implementation]] | ||
[[Category:Code Snippet]] | [[Category:Code Snippet]] | ||
| + | [[Category:Vulnerability]] | ||
Revision as of 12:00, 29 October 2008
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Last revision (mm/dd/yy): 10/29/2008
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
