Page History

Variadic functions can accept a variable number of arguments , but are problematic. Variadic functions define an implicit contract between the function writer and the function user that allows the function to determine the number of arguments passed passed in any particular invocation. Failure to exercise care when invoking a variadic function to ensure that it knows when to stop processing arguments enforce this contract may result in undefined behavior. See undefined behavior 141 of Appendix J of the C Standard.

Argument Processing

...

In the following code example, the variadic function {{average()}} is used to determine the average value of its passed integer arguments \[[Seacord 05c|AA. C References#Seacord 05c]\]. The function processes arguments until it finds one with a value of {{\-1}}. calculates the average value of the positive integer arguments passed to the function [Seacord 2013]. The function processes arguments until it encounters an argument with the value of va_eol (-1).

Code Block
enum { va_eol = -1 }; unsigned
Code Block
int average(int first, ...) { unsigned size_tint count = 0; unsigned int sum = 0; int i = first; va_list markerargs; va_start(markerargs, first); while (i != -1va_eol) { sum += i; count++; i = va_arg(markerargs, int); } va_end(markerargs); return(count ? (sum / count) : 0); }

Note that va_start() must be called to initialize the argument list and that va_end() must always be called when finished with a variable argument list.

Noncompliant Code Example

In this noncompliant code example, the average() However, if the function is called as follows:

int avg = average(1, 4, 6, 4, 1);

The omission of the -1 va_eol terminating value means that the function will continue to process values from the stack until it encounters a -1 va_eol by coincidence or an error occurs.

Compliant Solution

This compliant solution enforces the contract by adding va_eol as the final argument:

int avg = average(1, 4, 6, 4, 1, va_eol);

Noncompliant Code Example

Another common mistake is to use more format conversion specifiers than supplied arguments, as shown in this noncompliant code example:

const char *error_msg = "Resource not available to user.";
/* ... */
printf("Error (%s): %s", error_msg);

This code results in nonexistent arguments being processed by the function, potentially leaking information about the process.

Compliant Solution

This compliant solution matches the number of format specifiers with the number of variable arguments This results in undefined behavior, which could end up pulling extra values off the stack and unintentionally exposing data. The following example illustrates a case of this:

const char *error_msg = "Resource not available to user.";
/* ... */
printf("Error (%s): %s", error_msg);

Argument List Caveats

C99 C functions that accept the variadic primitive va_list as an argument pose an additional risk. Calls to vfprintf(), vfscanf(), vprintf(), vscanf(), vsnprintf(), vsprintf(), and vsscanf() use the va_arg() macro, invalidating the parameterized va_list. Consequently, once a va_list is passed as an argument to any of these functions, it cannot be used again except in without a call to the va_end() followed by a call to va_start() macro.

Risk Assessment

Incorrectly using a variadic function can result in abnormal program termination or unintended information disclosure.

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Automated Detection

...

Related Guidelines

Bibliography

...

Image Added Image Added Image Added

References

Wiki Markup\[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Section 7.15, "Variable arguments"; 7.19.6.8 "The {{vfprintf}} function" \[[Seacord 05c|AA. C References#Seacord 05c]\]