Description
The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.
While the interpretation of "large number of parameters" may vary for each product or developer, CISQ recommends a default maximum of 7 parameters/arguments.
Potential Impact
Other
Reduce Maintainability, Increase Analytical Complexity
Detection Methods
- Automated Static Analysis High — 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
Taxonomy Mappings
- OMG ASCMM: ASCMM-MNT-13 —
Frequently Asked Questions
What is CWE-1064?
CWE-1064 (Invokable Control Element with Signature Containing an Excessive Number of Parameters) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.
How can CWE-1064 be exploited?
Attackers can exploit CWE-1064 (Invokable Control Element with Signature Containing an Excessive Number of Parameters) to reduce maintainability, increase analytical complexity. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-1064?
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-1064?
CWE-1064 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.