This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Poor Style: Confusing Naming"

Jump to: navigation, search
Line 1: Line 1:
#REDIRECT [[Failure to follow guideline/specification]]
Line 8: Line 9:
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
Line 60: Line 58:
[[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]]
[[Category:OWASP ASDR Project]]
[[Category:Code Quality Vulnerability]]
[[Category:Code Snippet]]

Revision as of 16:22, 17 February 2009


#REDIRECT Failure to follow guideline/specification

ASDR Table of Contents

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


The class contains a field and a method with the same name.

It is confusing to have a member field and a method with the same name. It makes it easy for a programmer to accidentally call the method when attempting to access the field or vice versa.

Risk Factors



public class Totaller {
	  private int total;
	  public int total() {

Related Attacks

Related Vulnerabilities

Related Controls

Related Technical Impacts