CWE-683: Function Call With Incorrect Order of Arguments | Glexia
CWE-683 (Function Call With Incorrect Order of Arguments) weakness overview with consequences, detection methods, mitigations, related CVEs and MITRE ATT&CK context.
Glexia's Take · Automated analysis
CWE-683: Function Call With Incorrect Order of Arguments
Function Call With Incorrect Order of Arguments represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Other: Quality Degradation
Developer Pattern
CWE-683 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-683, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-683: Function Call With Incorrect Order of Arguments
The product 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.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.
Remediation
- Implementation: Use the function, procedure, or routine as specified.
Detection
- Automated Analysis: Because this function call often produces incorrect behavior, it will usually be detected during testing or normal operation of the product.
- Automated Analysis: Exercising 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.
Mappings
Related CVEs, CWEs, and ATT&CK context
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.