CWE-683: Function Call With Incorrect Order of Arguments

VariantDraft

The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-683 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-683, Function Call With Incorrect Order of Arguments, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Function Call With Incorrect Order of Arguments during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Analysis; recorded impacts include Quality Degradation. Use these source-defined anchors to turn CWE-683 into implementation, review, and verification checks for the affected component.

CWE-683: Function Call With Incorrect Order of Arguments — MITRE CWE

Triage CWE-683 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-683, Function Call With Incorrect Order of Arguments, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-683

Apply MITRE's full root-cause mapping guidance when using CWE-683, Function Call With Incorrect Order of Arguments. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-683 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-683, Function Call With Incorrect Order of Arguments. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-683: Function Call With Incorrect Order of Arguments?+

CWE-683: Function Call With Incorrect Order of Arguments is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Function Call With Incorrect Order of Arguments?+

If exploited, CWE-683 (Function Call With Incorrect Order of Arguments) it can compromise Other, leading to outcomes such as Quality Degradation.

How do you prevent or mitigate Function Call With Incorrect Order of Arguments?+

Recommended mitigations for CWE-683 include: Use the function, procedure, or routine as specified.

How is Function Call With Incorrect Order of Arguments detected?+

CWE-683 can be detected using Automated Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Function Call With Incorrect Order of Arguments?+

CWE-683 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Function Call With Incorrect Order of Arguments?+

MITRE documents real CVEs mapped to CWE-683, including CVE-2006-7049. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-683 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-683

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement
CWE-683: Function Call With Incorrect Order of Arguments | CWE Lookup | InventiveHQ