Function Call With Incorrect Number of Arguments |
Weakness ID: 685 (Weakness Variant) | Status: Draft |
Description Summary
This problem typically occurs when the programmer makes a typo, or copy and paste errors. |
Other While this weakness might be caught by the compiler in some languages, it can occur more frequently in cases in which the called function accepts variable numbers of arguments, such as format strings in C. It also can occur in languages or environments that do not require that functions always be called with the correct number of arguments, such as Perl. |
Use the function, procedure, routine as specified. |
Because this function call often produces incorrect behavior it will usually be detected during testing or normal operation of the software. During testing exercise all possible control paths will typically expose this weakness except in rare cases when the incorrect function call accidentally produces the correct results or if the provided argument type is very similar to the expected argument type. |
Ordinality | Description |
---|---|
Primary | (where the weakness exists independent of other weaknesses) |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 628 | Function Call with Incorrectly Specified Arguments | Development Concepts (primary)699 Research Concepts (primary)1000 |
Modifications | ||||
---|---|---|---|---|
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Potential Mitigations | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Applicable Platforms, Detection Factors, Relationships, Other Notes, Weakness Ordinalities | ||||
2009-05-27 | CWE Content Team | MITRE | Internal | |
updated Description | ||||
2009-10-29 | CWE Content Team | MITRE | Internal | |
updated Modes of Introduction, Other Notes, Potential Mitigations |