Read Time:34 Second
Description
The software calls a function, procedure, or routine, but the caller specifies too many arguments, or too few arguments, which may lead to undefined behavior and resultant weaknesses.
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Other: Quality Degradation
Potential Mitigations
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.