CWE-1099
Weakness ProhibitedInconsistent Naming Conventions for Identifiers
Abstraction: Base · Status: Incomplete
The product's code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callables, I/O capabilities, data types, file names, or similar types of elements.
Mapping guidance
This entry is primarily a quality issue with no direct security implications.
Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.
Modes of introduction
Detection methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Content history
Entry derived from Common Quality Enumeration (CQE) Draft 0.9.
updated Relationships
updated Description
updated Relationships
updated Mapping_Notes
updated Mapping_Notes
updated Applicable_Platforms, Common_Consequences, Description, Detection_Factors, Time_of_Introduction
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.