According to the C Standard, Annex J, J.2 [ISO/IEC 9899:2011], the behavior of a program is undefined in the circumstances outlined in the following table. The "Guideline" column in the table identifies the coding practices that address the specific case of undefined behavior (UB). The descriptions of undefined behaviors in the "Description" column are direct quotes from the standard. The parenthesized numbers refer to the subclause of the C Standard (C11) that identifies the undefined behavior.
UB | Class | Description | Guideline |
---|---|---|---|
1 | A "shall" or "shall not" requirement that appears outside of a constraint is violated (clause 4). | ||
2 | A nonempty source file does not end in a new-line character which is not immediately preceded by a backslash character or ends in a partial preprocessing token or comment (5.1.1.2). | ||
3 | Token concatenation produces a character sequence matching the syntax of a universal character name (5.1.1.2). | ||
4 | A program in a hosted environment does not define a function named | ||
5 | The execution of a program contains a data race (5.1.2.4). | ||
6 | A character not in the basic source character set is encountered in a source file, except in an identifier, a character constant, a string literal, a header name, a comment, or a preprocessing token that is never converted to a token (5.2.1). | ||
7 | An identifier, comment, string literal, character constant, or header name contains an invalid multibyte character or does not begin and end in the initial shift state (5.2.1.2). | ||
8 | The same identifier has both internal and external linkage in the same translation unit (6.2.2). | ||
9 | An object is referred to outside of its lifetime (6.2.4). | ||
10 | The value of a pointer to an object whose lifetime has ended is used (6.2.4). | ||
11 | The value of an object with automatic storage duration is used while it is indeterminate (6.2.4, 6.7.9, 6.8). | ||
12 | A trap representation is read by an lvalue expression that does not have character type (6.2.6.1). | ||
13 | A trap representation is produced by a side effect that modifies any part of the object using an lvalue expression that does not have character type (6.2.6.1). | ||
14 | The operands to certain operators are such that they could produce a negative zero result, but the implementation does not support negative zeros (6.2.6.2). | ||
15 | Two declarations of the same object or function specify types that are not compatible (6.2.7). | ||
16 | A program requires the formation of a composite type from a variable length array type whose size is specified by an expression that is not evaluated (6.2.7). | ||
17 | Conversion to or from an integer type produces a value outside the range that can be represented (6.3.1.4). | ||
18 | Demotion of one real floating type to another produces a value outside the range that can be represented (6.3.1.5). | ||
19 | An lvalue does not designate an object when evaluated (6.3.2.1). | ||
20 | A non-array lvalue with an incomplete type is used in a context that requires the value of the designated object (6.3.2.1). | ||
21 | An lvalue designation an object of automatic storage duration that could have been declared with the register storage class is used in a context that requires the value of the designated object, but the object is uninitialized (6.3.2.1). | ||
22 | An lvalue having array type is converted to a pointer to the initial element of the array, and the array object has | ||
23 | An attempt is made to use the value of a void expression, or an implicit or explicit conversion (except to | ||
24 | Conversion of a pointer to an integer type produces a value outside the range that can be represented (6.3.2.3). | ||
25 | Conversion between two pointer types produces a result that is incorrectly aligned (6.3.2.3). | ||
26 | A pointer is used to call a function whose type is not compatible with the pointed-to type (6.3.2.3). | EXP37-C | |
27 | An unmatched | ||
28 | A reserved keyword token is used in translation phase 7 or 8 for some purpose other than as a keyword (6.4.1). | ||
29 | A universal character name in an identifier does not designate a character whose encoding falls into one of the specified ranges (6.4.2.1). | ||
30 | The initial character of an identifier is a universal character name designating a digit (6.4.2.1). | ||
31 | Two identifiers differ only in nonsignificant characters (6.4.2.1). | ||
32 | The identifier | ||
33 | The program attempts to modify a string literal (6.4.5). | ||
34 | The characters | ||
35 | A side effect on a scalar object is unsequenced relative to either a different side effect on the same scalar object or a value computation using the value of the same scalar object (6.5). | ||
36 | An exceptional condition occurs during the evaluation of an expression (6.5). | ||
37 | An object has its stored value accessed other than by an lvalue of an allowable type (6.5). | ||
38 | For a call to a function without a function prototype in scope, the number of arguments does not equal the number of parameters (6.5.2.2). | ||
39 | For call to a function without a function prototype in scope where the function is defined with a function prototype, either the prototype ends with an ellipsis or the types of the arguments after promotion are not compatible with the types of the parameters (6.5.2.2). | ||
40 | For a call to a function without a function prototype in scope where the function is not defined with a function prototype, the types of the arguments after promotion are not compatible with those of the parameters after promotion (with certain exceptions) (6.5.2.2). | EXP37-C | |
41 | A function is defined with a type that is not compatible with the type (of the expression) pointed to by the expression that denotes the called function (6.5.2.2). | ||
42 | A member of an atomic structure or union is accessed (6.5.2.3). | ||
43 | The operand of the unary | ||
44 | A pointer is converted to other than an integer or pointer type (6.5.4). | ||
45 | The value of the second operand of the | ||
46 | Addition or subtraction of a pointer into, or just beyond, an array object and an integer type produces a result that does not point into, or just beyond, the same array object (6.5.6). | ||
47 | Addition or subtraction of a pointer into, or just beyond, an array object and an integer type produces a result that points just beyond the array object and is used as the operand of a unary | ||
48 | Pointers that do not point into, or just beyond, the same array object are subtracted (6.5.6). | ||
49 | An array subscript is out of range, even if an object is apparently accessible with the given subscript (as in the lvalue expression | ||
50 | The result of subtracting two pointers is not representable in an object of type | ||
51 | An expression is shifted by a negative number or by an amount greater than or equal to the width of the promoted expression (6.5.7). | ||
52 | An expression having signed promoted type is left-shifted and either the value of the expression is negative or the result of shifting would not be representable in the promoted type (6.5.7). | ||
53 | Pointers that do not point to the same aggregate or union (nor just beyond the same array object) are compared using relational operators (6.5.8). | ||
54 | An object is assigned to an inexactly overlapping object or to an exactly overlapping object with incompatible type (6.5.16.1). | ||
55 | An expression that is required to be an integer constant expression does not have an integer type; has operands that are not integer constants, enumeration constants, character constants, | ||
56 | A constant expression in an initializer is not, or does not evaluate to, one of the following: an arithmetic constant expression, a null pointer constant, an address constant, or an address constant for an object type plus or minus an integer constant expression (6.6). | ||
57 | An arithmetic constant expression does not have arithmetic type; has operands that are not integer constants, floating constants, enumeration constants, character constants, or | ||
58 | The value of an object is accessed by an array-subscript | ||
59 | An identifier for an object is declared with no linkage and the type of the object is incomplete after its declarator, or after its init-declarator if it has an initializer (6.7). | ||
60 | A function is declared at block scope with an explicit storage-class specifier other than | ||
61 | A structure or union is defined as containing no named members (6.7.2.1). | ||
62 | An attempt is made to access, or generate a pointer to just past, a flexible array member of a structure when the referenced object provides no elements for that array (6.7.2.1). | ||
63 | When the complete type is needed, an incomplete structure or union type is not completed in the same scope by another declaration of the tag that defines the content (6.7.2.3). | ||
64 | An attempt is made to modify an object defined with a | ||
65 | An attempt is made to refer to an object defined with a | ||
66 | The specification of a function type includes any type qualifiers (6.7.3). | ||
67 | Two qualified types that are required to be compatible do not have the identically qualified version of a compatible type (6.7.3). | ||
68 | An object which has been modified is accessed through a | ||
69 | A | ||
70 | A function with external linkage is declared with an | ||
71 | A function declared with a _Noreturn function specifier returns to its caller (6.7.4). | ||
72 | The definition of an object has an alignment specifier and another declaration of that object has a different alignment specifier (6.7.5). | ||
73 | Declarations of an object in different translation units have different alignment specifiers (6.7.5). | ||
74 | Two pointer types that are required to be compatible are not identically qualified, or are not pointers to compatible types (6.7.6.1). | ||
75 | The size expression in an array declaration is not a constant expression and evaluates at program execution time to a nonpositive value (6.7.6.2). | ||
76 | In a context requiring two array types to be compatible, they do not have compatible element types, or their size specifiers evaluate to unequal values (6.7.6.2). | EXP39-C | |
77 | A declaration of an array parameter includes the keyword | ||
78 | A storage-class specifier or type qualifier modifies the keyword | ||
79 | In a context requiring two function types to be compatible, they do not have compatible return types, or their parameters disagree in use of the ellipsis terminator or the number and type of parameters (after default argument promotion, when there is no parameter type list or when one type is specified by a function definition with an identifier list) (6.7.6.3). | ||
80 | The value of an unnamed member of a structure or union is used (6.7.9). | ||
81 | The initializer for a scalar is neither a single expression nor a single expression enclosed in braces (6.7.9). | ||
82 | The initializer for a structure or union object that has automatic storage duration is neither an initializer list nor a single expression that has compatible structure or union type (6.7.9). | ||
83 | The initializer for an aggregate or union, other than an array initialized by a string literal, is not a brace-enclosed list of initializers for its elements or members (6.7.9). | ||
84 | An identifier with external linkage is used, but in the program there does not exist exactly one external definition for the identifier, or the identifier is not used and there exist multiple external definitions for the identifier (6.9). | ||
85 | A function definition includes an identifier list, but the types of the parameters are not declared in a following declaration list (6.9.1). | ||
86 | An adjusted parameter type in a function definition is not an object type (6.9.1). | ||
87 | A function that accepts a variable number of arguments is defined without a parameter type list that ends with the ellipsis notation (6.9.1). | ||
88 | The | ||
89 | An identifier for an object with internal linkage and an incomplete type is declared with a tentative definition (6.9.2). | ||
90 | The token defined is generated during the expansion of a | ||
91 | The | ||
92 | The character sequence in an | ||
93 | There are sequences of preprocessing tokens within the list of macro arguments that would otherwise act as preprocessing directives (6.10.3). | ||
94 | The result of the preprocessing operator | ||
95 | The result of the preprocessing operator | ||
96 | The | ||
97 | A non- | ||
98 | A | ||
99 | The name of a predefined macro, or the identifier defined, is the subject of a | ||
100 | An attempt is made to copy an object to an overlapping object by use of a library function, other than as explicitly allowed (e.g., | ||
101 | A file with the same name as one of the standard headers, not provided as part of the implementation, is placed in any of the standard places that are searched for included source files (7.1.2). | ||
102 | A header is included within an external declaration or definition (7.1.2). | ||
103 | A function, object, type, or macro that is specified as being declared or defined by some standard header is used before any header that declares or defines it is included (7.1.2). | ||
104 | A standard header is included while a macro is defined with the same name as a keyword (7.1.2). | ||
105 | The program attempts to declare a library function itself, rather than via a standard header, but the declaration does not have external linkage (7.1.2). | ||
106 | The program declares or defines a reserved identifier, other than as allowed by 7.1.4 (7.1.3). | ||
107 | The program removes the definition of a macro whose name begins with an underscore and either an uppercase letter or another underscore (7.1.3). | ||
108 | An argument to a library function has an invalid value or a type not expected by a function with a variable number of arguments (7.1.4). | ||
109 | The pointer passed to a library function array parameter does not have a value such that all address computations and object accesses are valid (7.1.4). | ||
110 | The macro definition of | ||
111 | The argument to the | ||
112 | The | ||
113 | The value of an argument to a character handling function is neither equal to the value of | ||
114 | A macro definition of | ||
115 | Part of the program tests floating-point status flags, sets floating-point control modes, or runs under non-default mode settings, but was translated with the state for the | ||
116 | The exception-mask argument for one of the functions that provide access to the floating-point status flags has a nonzero value not obtained by bitwise OR of the floating-point exception macros (7.6.2). | ||
117 | The | ||
118 | The argument to | ||
119 | The value of the result of an integer arithmetic or conversion function cannot be represented (7.8.2.1, 7.8.2.2, 7.8.2.3, 7.8.2.4, 7.22.6.1, 7.22.6.2, 7.22.1). | ||
120 | The program modifies the string pointed to by the value returned by the | ||
121 | The program modifies the structure pointed to by the value returned by the | ||
122 | A macro definition of | ||
123 | An argument to a floating-point classification or comparison macro is not of real floating type (7.12.3, 7.12.14). | ||
124 | A macro definition of | ||
125 | An invocation of the | ||
126 | The | ||
127 | After a | ||
128 | The program specifies an invalid pointer to a signal handler function (7.14.1.1). | ||
129 | A signal handler returns when the signal corresponded to a computational exception (7.14.1.1). | ||
130 | A signal handler called in response to SIGFPE , SIGILL , SIGSEGV , or any other implementation-defined value corresponding to a computational exception returns (7.14.1.1). | SIG35-C | |
131 | A signal occurs as the result of calling the | ||
132 | A signal occurs other than as the result of calling the abort or raise function, and the signal handler refers to an object with static or thread storage duration that is not a lock-free atomic object other than by assigning a value to an object declared as volatile sig_atomic_t, or calls any function in the standard library other than the abort function, the _Exit function, the quick_exit function, or the signal function (for the same signal number) (7.14.1.1). | ||
133 | The value of | ||
134 | A signal is generated by an asynchronous signal handler (7.14.1.1). | ||
135 | The signal function is used in a multi-threaded program (7.14.1.1). | CON37-C | |
136 | A function with a variable number of arguments attempts to access its varying arguments other than through a properly declared and initialized | ||
137 | The macro | ||
138 | A macro definition of | ||
139 | The | ||
140 | The type parameter to the | ||
141 | The | ||
142 | The | ||
143 | The parameter parmN of a | ||
144 | The member designator parameter of an | ||
145 | The argument in an instance of one of the integer-constant macros is not a decimal, octal, or hexadecimal constant, or it has a value that exceeds the limits for the corresponding type (7.20.4). | ||
146 | A byte input/output function is applied to a wide-oriented stream, or a wide character input/output function is applied to a byte-oriented stream (7.21.2). | ||
147 | Use is made of any portion of a file beyond the most recent wide character written to a wide-oriented stream (7.21.2). | ||
148 | The value of a pointer to a | ||
149 | The stream for the | ||
150 | The string pointed to by the mode argument in a call to the | ||
151 | An output operation on an update stream is followed by an input operation without an intervening call to the | ||
152 | An attempt is made to use the contents of the array that was supplied in a call to the | ||
153 | There are insufficient arguments for the format in a call to one of the formatted input/output functions, or an argument does not have an appropriate type (7.21.6.1, 7.21.6.2, 7.29.2.1, 7.29.2.2). | ||
154 | The format in a call to one of the formatted input/output functions or to the | ||
155 | In a call to one of the formatted output functions, a precision appears with a conversion specifier other than those described (7.21.6.1, 7.29.2.1). | ||
156 | A conversion specification for a formatted output function uses an asterisk to denote an argument-supplied field width or precision, but the corresponding argument is not provided (7.21.6.1, 7.29.2.1). | ||
157 | A conversion specification for a formatted output function uses a | ||
158 | A conversion specification for one of the formatted input/output functions uses a length modifier with a conversion specifier other than those described (7.21.6.1, 7.21.6.2, 7.29.2.1, 7.29.2.2). | ||
159 | An | ||
160 | An | ||
161 | A | ||
162 | An invalid conversion specification is found in the format for one of the formatted input/output functions, or the | ||
163 | The number of characters or wide characters transmitted by a formatted output function (or written to an array, or that would have been written to an array) is greater than INT_MAX (7.21.6.1, 7.29.2.1). | ||
164 | The number of input items assigned by a formatted input function is greater than | ||
165 | The result of a conversion by one of the formatted input functions cannot be represented in the corresponding object, or the receiving object does not have an appropriate type (7.21.6.2, 7.29.2.2). | ||
166 | A | ||
167 | A | ||
168 | The input item for a | ||
169 | The | ||
170 | The contents of the array supplied in a call to the | ||
171 | The file position indicator for a binary stream is used after a call to the | ||
172 | The file position indicator for a stream is used after an error occurred during a call to the | ||
173 | A partial element read by a call to the | ||
174 | The | ||
175 | The | ||
176 | A non-null pointer returned by a call to the | ||
177 | The value of a pointer that refers to space deallocated by a call to the | ||
178 | The alignment requested of the aligned_alloc function is not valid or not supported by the implementation, or the size requested is not an integral multiple of the alignment (7.22.3.1). | ||
179 | The pointer argument to the | ||
180 | The value of the object allocated by the | ||
181 | The values of any bytes in a new object allocated by the | ||
182 | The program calls the exit or quick_exit function more than once, or calls both functions (7.22.4.4, 7.22.4.7). | ERR04-C | |
183 | During the call to a function registered with the atexit or at_quick_exit function, a call is made to the longjmp function that would terminate the call to the registered function (7.22.4.4, 7.22.4.7). | ||
184 | The string set up by the | ||
185 | A signal is raised while the quick_exit function is executing (7.22.4.7). | ||
186 | A command is executed through the | ||
187 | A searching or sorting utility function is called with an invalid pointer argument, even if the number of elements is zero (7.22.5). | ||
188 | The comparison function called by a searching or sorting utility function alters the contents of the array being searched or sorted, or returns ordering values inconsistently (7.22.5). | ||
189 | The array being searched by the | ||
190 | The current conversion state is used by a multibyte/wide character conversion function after changing the | ||
191 | A string or wide string utility function is instructed to access an array beyond the end of an object (7.24.1, 7.29.4). | ||
192 | A string or wide string utility function is called with an invalid pointer argument, even if the length is zero (7.24.1, 7.29.4). | ||
193 | The contents of the destination array are used after a call to the | ||
194 | The first argument in the very first call to the | ||
195 | The type of an argument to a type-generic macro is not compatible with the type of the corresponding parameter of the selected function (7.25). | ||
196 | A complex argument is supplied for a generic parameter of a type-generic macro that has no corresponding complex function (7.25). | ||
197 | At least one member of the broken-down time passed to asctime contains a value outside its normal range, or the calculated year exceeds four digits or is less than the year 1000 (7.27.3.1). | ||
198 | The argument corresponding to an | ||
199 | In a call to the | ||
200 | An | ||
201 | The value of an argument of type | ||
202 | The | ||
203 | The |
Graphical symbols used in the preceding table:
Symbol | C11 Classification |
---|---|
Critical Undefined Behavior | |
Bounded Undefined Behavior | |
Undefined Behavior (information/confirmation needed) | |
Possible Conforming Language Extension |
13 Comments
Beomyeon Cho
hi, i'm beginner in CERT C Coding Standard, and I have two questions.
First, there are 58 unspecified behaviors and 203 undefined behavior in C11.
and according to this page, it seems that only 8 of 58 unspecified behaviors and 75 of 203 undefined behaviors can be avoided by complying with CERT C Coding Standard, is it right?
I wonder whether it is true or not.
Second, if it is true, it might be too weak to apply CERT C to some safety-critical systems which i'm going to develop considering CERT C Coding Standard is a necessary not sufficient set of rules for developing safe, reliable and secure systems.
in order to be applied to develop safety-critical systems, i think there should be huge updates or great changes and i seriously wonder the plan.
is there anybody who can help me?
I will appreciate your advices and help.
Aaron Ballman
I am not certain that this page has been kept up to date with the list of secure coding rules, but the possibility still exists that we do not have rules covering all instances of undefined behavior in the C Standard.
You are correct that the CERT secure coding rules are not intended to be used for safety-critical systems (we call this out in the Front Matter section in a few places, such as System Qualities), except as a companion piece. We do not currently intend to support the safety-critical space with this coding standard, but there are other standards which give guidance in that space (such as MISRA C).
Beomyeon Cho
yes... i read Front Matter section and i know that CERT C Coding Standard was not for safe system at the beginning. However since 2004, second edition, the keywords 'safe', and 'reliable' has inserted into title.
when it compared to MISRA C, the gap is shocking. MISRA C covers 43 unspecified behaviors among 50 in C99 and 183 undefined behaviors among 191 in C99
so now i'm little bit confused and i want to know how to read these tables.(in MISRA C,there are lots of blanks too but the blanks doesn't mean 'not cover'.
Does blank mean 'not cover' in these tables of CERT C? Is there anybody who know how to interpret these tables?
Aaron Ballman
In the table above, a blank in the last column means that we have not mapped the information in the row on to a specific CERT C Coding Standard guideline. That doesn't mean we don't cover the UB, but it does mean that we've not formalized the mapping. For instance, I notice that UB 19 is covered by EXP33-C. Do not read uninitialized memory, despite it being a blank in the table.
Beomyeon Cho
oh is it true? then why has these tables not been update?
hmm.. I really want to know full tables...
Is there any way I can know that?
Aaron Ballman
I suspect the table got out of sync due to bit rot as we added information to the coding standard, and we do not currently have funding to work on the CERT C Coding Standard aside from basic maintenance. No one has taken a comprehensive pass over the rules recently to perform the updates to the table, but we would welcome contributions from anyone willing to put in the effort.
David A.D. Morano
The guideline for UB 137 is currently specified as CON37-C. Is this a typo? Should instead UB 135 have the guideline CON37-C (and UB 137 guideline left blank)?
David Svoboda
Yes, I fixed it, thanks.
Avinash Sonawane
UB 151: "output operation with an intervening call" should be changed to "output operation without an intervening call"
David Svoboda
Avinash Sonawane I have good news and bad news:
First, this is directly quoting from ISO C Annex J, and our quotation is correct...that is Annex J says "with an intervening call", not "without".
Second, my studying of ISO C has convinced me that you are correct, and it should be "without" not "with". I'll file a DefectReport with the ISO C committee.
I'll let you decide which is the good news :)
Avinash Sonawane
I think it's a bad news that ISO C Annex J contradicts section 7.21.5.3 of the same standard.
> I'll file a DefectReport with the ISO C committee.
Cool! This is a good news.
Ding Fei
#32 The identifier
func{}
is explicitly declared (6.4.2.2).=>
#32 The identifier _ _func_ _ is explicitly declared (6.4.2.2).
David Svoboda
Fixed, thanks.