The C standard Standard allows an array variable to be declared both with a dimension bound index and with an initialization literal. The initialization literal also implies an array size , in the number of elements specified. For strings, the size specified by a string literal is the number of characters in the literal plus one for the terminating null character.
It is common for an array variable to be declared with both initialized by a string literal , and a size index which specifies 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 [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 . This is one too few characters to hold the string , since because it does not account for the terminating null character. Such a sequence of characters has limited utility and has the potential to cause vulnerabilities if a null-terminated byte string is assumed. As a result, the size index for a character array must never be explicit.
A better approach is to not specify the dimension bound of a string initialized with a string literal , as because the compiler will automatically allocate sufficient space for the entire string literal, including the terminating null character.
Incidentally, initializing a character array using a string literal to fit exactly without a null byte is not allowed in C++.
Non-Compliant Code Example
This rule is a specific exception to ARR02-C. Explicitly specify array bounds, even if implicitly defined by an initializer.
Noncompliant Code Example
This noncompliant code example The following non-compliant code initializes an array of characters using a string literal that defines one character more character (counting the terminating '\0'
) than the array can hold.:
Code Block | ||||
---|---|---|---|---|
| ||||
const char s[3] = "abc"; |
The size of the array s
is three3, although the size of the string literal is four4. 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.)
Implementation Details
This code compiles with no warning with Visual Studio 2013 and GCC 4.8.1. It produces a three-character array with no terminating null character, as specified by the standard.
Compliant Solution
This compliant solution does not specify the dimension bound of a character array in the array declaration. By omitting the size, the array will automatically be of appropriate length If the array bound is omitted, the compiler allocates sufficient storage to store the full entire string literal, including the terminating null character.
Code Block | ||||
---|---|---|---|---|
| ||||
const char s[] = "abc"; |
This is the approach is preferred approach, because the size of the array can always be derived even if the size of the string literal changes.
Exceptions
STR36STR11-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 */ |
Again, if one is providing an initializer to an array, an explicit dimension is unnecessary, and, in fact, discouraged.
Also, one 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- |
high
probable
low
P18
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.
References
Wiki Markup |
---|
\[[ISO/IEC 9899:1999|AA. C References#ISO/IEC 9899-1999]\]
\[[Seacord 05a|AA. C References#Seacord 05a]\] Chapter 2, "Strings"
[The Embedded C++ Programming Guide Lines|http://www.caravan.net/ec2plus/guide.html]. Version WP-GU-003. 6,Jan 1998 by the Embedded C++ Technical Committee A.8 Character array initialization |
Related Guidelines
Bibliography
[ECTC 1998] | Section A.8, "Character Array Initialization" |
[ISO/IEC 9899:2011] | Subclause 6.7.9, "Initialization" |
[Seacord 2013] | Chapter 2, "Strings" |
...
STR35-C. Do not copy data from an unbounded source to a fixed-length array 07. Characters and Strings (STR) STR37-C. Arguments to character handling functions must be representable as an unsigned char