...
Passing an object of an unsupported type as the second argument to va_start() can result in undefined behavior that might be exploited to cause data integrity violations.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
EXP58-CPP | Medium | Unlikely | Medium | P4 |
L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Clang |
| -Wvarargs | Does not catch the violation in the third noncompliant code example (it is conditionally supported by Clang) | ||||||
| CodeSonar |
| BADMACRO.STDARG_H | Use of <stdarg.h> Feature | ||||||
| Helix QAC |
| C++3852, C++3853 | |||||||
| Klocwork |
| CERT.VA_START.TYPE | |||||||
| Parasoft C/C++test |
| CERT_CPP-EXP58-a | Use macros for variable arguments correctly | ||||||
| Polyspace Bug Finder |
| CERT C++: EXP58-CPP | Checks for incorrect data types for second argument of va_start (rule fully covered) |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
Bibliography
| [ISO/IEC 9899:2011] | Subclause 7.16.1.4, "The va_start Macro" |
| [ISO/IEC 14882-2014] | Subclause 18.10, "Other Runtime Support" |
...
...