Function Call With Incorrectly Specified Argument Value
The software calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses.
The following examples help to illustrate the nature of this weakness and describe methods or techniques which can be used to mitigate the risk.
Note that the examples here are by no means exhaustive and any given weakness may have many subtle varieties, each of which may require different detection methods or runtime controls.
This Perl code intends to record whether a user authenticated successfully or not, and to exit if the user fails to authenticate. However, when it calls ReportAuth(), the third argument is specified as 0 instead of 1, so it does not exit.
This category identifies Software Fault Patterns (SFPs) within the Glitch in Computation cluster (SFP1).
This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Command cluster (SFP24).
Weaknesses in this category are related to rules in the Memory Management (MEM) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific wea...
This view (slice) covers all the elements in CWE.
This view (slice) lists weaknesses that can be introduced during implementation.