Description
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.
Potential Impact
Other
Reduce Maintainability, Increase Analytical Complexity
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 sea
Related Weaknesses
Frequently Asked Questions
What is CWE-1099?
CWE-1099 (Inconsistent Naming Conventions for Identifiers) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. 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,...
How can CWE-1099 be exploited?
Attackers can exploit CWE-1099 (Inconsistent Naming Conventions for Identifiers) to reduce maintainability, increase analytical complexity. This weakness is typically introduced during the Implementation, Documentation phase of software development.
How do I prevent CWE-1099?
Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.
What is the severity of CWE-1099?
CWE-1099 is classified as a Base-level weakness (Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.