...
It is common for an array variable to be initialized by a string literal and declared with an explicit bound that matches the number of characters in the string literal. Subclause 6.7.9, paragraph 14, of the C Standard [AA. Bibliography#ISO-ISO/IEC 9899-:2011], says:
An array of character type may be initialized by a character string literal or UTF−8 string literal, optionally enclosed in braces. Successive bytes of the string literal (including the terminating null character if there is room or if the array is of unknown size) initialize the elements of the array.
However, if the string is intended to be used as a null-terminated byte string, then the array will have one too few characters to hold the string because it does not account for the terminating null character. Such a sequence of characters has limited utility and has the potential to cause BB. Definitions#vulnerability vulnerabilities if a null-terminated byte string is assumed.
A better approach is to not specify the bound of a string initialized with a string literal because the compiler will automatically allocate sufficient space for the entire string literal, including the terminating null character. This rule is a specific exception to ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer.
Noncompliant Code Example
...
Code Block | ||||
---|---|---|---|---|
| ||||
const char s[3] = "abc";
|
The size of the array s
is 3, although the size of the string literal is 4. Any subsequent use of the array as a null-terminated byte string can result in a vulnerability, because s
is not properly null-terminated. (See STR32-C. Do not pass a non-null-terminated character sequence to a library function that expects a string.)
...
Code Block | ||||
---|---|---|---|---|
| ||||
const char s[] = "abc";
|
This approach is preferred because the size of the array can always be derived even if the size of the string literal changes.
Exceptions
STR11-C-EX1: If the intention is to create a character array and not a null-terminated byte string, initializing to fit exactly without a null byte is allowed but not recommended. The preferred approach to create an array containing just the three characters 'a'
, 'b'
, and 'c'
, for example, is to declare each character literal as a separate element as follows:
Code Block | ||||
---|---|---|---|---|
| ||||
char s[3] = { 'a', 'b', 'c' }; /* NOT a string */
|
Also, you should make clear in comments or documentation if a character array is, in fact, not a null-terminated byte string.
STR11-C-EX2: If the character array must be larger than the string literal it is initialized with, you may explicitly specify an array bounds. This is particularly important if the array's contents might change during program execution.
Code Block | ||||
---|---|---|---|---|
| ||||
#include <string.h>
void func(void) {
char s[10] = "abc";
strcpy(&s[3], "def");
} |
Risk Assessment
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
STR11-C | Low | Probable | Low | P6 | L2 |
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Astrée |
| Supported: Astrée can detect subsequent code defects that this rule aims to prevent. | |||||||
Axivion Bauhaus Suite |
| CertC-STR11 | |||||||
Compass/ROSE |
| CC2.STR36 | Fully implemented |
Helix QAC |
| C1312 | |||||||
LDRA tool suite |
| 404 S | Partially implemented |
Parasoft C/C++test |
| CERT_C-STR11-a | Do not specify the bound of a character array initialized with a string literal | ||||||
PC-lint Plus |
| 784 | Partially supported | ||||||
Polyspace Bug Finder |
| Checks for missing null in string array (rec. partially covered) |
Splint |
|
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
ISO/IEC TR 24772 |
:2013 | String Termination [CJM] |
Bibliography
[ |
ECTC 1998] | Section A.8, "Character Array Initialization" |
[ |
ISO/IEC 9899 |
:2011] | Subclause 6.7.9, "Initialization" |
[ |
Seacord 2013] | Chapter 2, "Strings" |
...
...