Detail CWE-683

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

Mode Pengenalan

Implementation : This problem typically occurs when the programmer makes a typo, or copy and paste errors. 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.

Platform yang Berlaku

Bahasa

Kelas: Not Language-Specific (Undetermined)

Konsekuensi Umum

Contoh yang Diamati

Mitigasi yang Memungkinkan

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

Metode Deteksi

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.

Catatan Pemetaan Kerentanan

Justifikasi : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Pengajuan

Modifikasi