If a file with the same name as a standard file name header is placed in the search path for included source files, the behavior is undefined.
The following table from the C Standard, subclause 7.1.2 [ISO/IEC 9899:2011], lists these standard headers are:
<complex<ctype<errno<fenv<float<complex.h> | <inttypes.h> | <setjmp.h> |
<iso646<limits<locale<math<setjmp<stdarg<stddef.h> | <string.h> | <wchar.h> |
<errno.h> |
<stdbool<stddef<stdalign.h> | <stdint.h> | <tgmath.h> |
<stdio<stdlib<string<tgmath<time<wchar <wctype.h> | Do not reuse standard header file names, system-specific header file names, or other header file names.
Noncompliant Code Example
In this noncompliant code example, the programmer chooses to use a local version of the standard library but does not make the change clear:
| Code Block |
|---|
|
#include "stdio.h" /* Confusing, distinct from <stdio.h> */
/* ... */
|
Compliant Solution
The solution addresses the problem by giving the local library a unique name (per PRE08-C. Guarantee that header file names are unique), which makes it apparent that the library used is not the original:
| Code Block |
|---|
|
/* Using a local version of stdio.h */
#include "mystdio.h"
/* ... */
|
Risk Assessment
Using header file names that conflict with the C standard library functions other header file names can result in not including the intended filean incorrect file being included.
Rule Recommendation | Severity | Likelihood |
|---|
Remediation Cost Detectable | Repairable | Priority | Level |
|---|
PRE04 |
-A 1 (low) | 1 (unlikely) | 3 (low) | P3 | L3 Automated Detection
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
References
...
Related Guidelines
Bibliography
...
...
...
...
...
...
Image Added Image Added Image Added
