Function Call With Incorrect Number of Arguments

When a function is called with an incorrect argument count, the underlying system mechanics break down. The calling code and the function have mismatched expectations about how data is arranged on the stack or in registers. This can lead to the function reading invalid values, interpreting data incorrectly (like treating a string as a pointer), or corrupting adjacent memory. The immediate result is often undefined behavior, which can manifest as crashes, data corruption, or unexpected program flow. From a security perspective, this flaw is a gateway for more severe exploits. An attacker might manipulate this mismatch to leak sensitive data from memory, bypass security checks, or execute arbitrary code. It's commonly seen in languages that don't enforce strict type checking at compile-time (like C or C++), in cases of incorrect function pointer usage, or when interfacing with external libraries. Developers must ensure function signatures are always correctly matched, especially when using dynamic linking or callback mechanisms.