Description
The software calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.
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 or types of arguments, such as format strings in C. It also can occur in languages or environments that do not enforce strong typing.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Other: Quality Degradation
Potential Mitigations
Phase: Implementation
Description:
Use the function, procedure, or routine as specified.
Phase: Testing
Description:
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.
CVE References
- CVE-2006-7049
- Application calls functions with arguments in the wrong order, allowing attacker to bypass intended access restrictions.