COMMON WEAKNESS ENUMERATIONDraft

CWE-628

Function Call with Incorrectly Specified Arguments

The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.

Extended description

There are multiple ways in which this weakness can be introduced, including: - the wrong variable or reference; - an incorrect number of arguments; - incorrect order of arguments; - wrong type of arguments; or - wrong value.

Root cause

How and when does the problem arise?

Lifecycle phase

Implementation

Risk

What does successful exploitation lead to?

Quality DegradationGain Privileges or Assume Identity

Affected security scopes: Other, Access Control

This weakness can cause unintended behavior and can lead to additional weaknesses such as allowing an attacker to gain unintended access to system resources.

Defence

How is it prevented and fixed?

Build and Compilation

Build and Compilation aşaması savunması

Detail
Once found, these issues are easy to fix. Use code inspection tools and relevant compiler features to identify potential violations. Pay special attention to code that is not likely to be exercised heavily during QA.

Architecture and Design

Architecture and design approach

Detail
Make sure your API's are stable before you use them in production code.

Verification

How is it detected?

Other

Since these bugs typically introduce incorrect behavior that is obvious to users, they are found quickly, unless they occur in rarely-tested code paths. Managing the correct number of arguments can be made more difficult in cases where format strings are used, or when variable numbers of arguments are supported.