CWE-683: Function Call With Incorrect Order of Arguments

Variant

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.

Consequences

Other: Quality Degradation

How to prevent it

Implementation: Use the function, procedure, or routine as specified.

Recent advisories

GHSA-69xg-f649-w5g2 — Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint
GHSA-ph9x-4vc9-m39g — Vyper vulnerable to incorrect ordering of arguments for kwargs passed to internal calls

All advisories for CWE-683

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor