Page History

When a guideline has been deprecated, it will remain available until the next major release at which point it will be moved to

The managed string library described in Specifications for Managed Strings [Burch 2006] was developed in response to the need for a string library that could improve the quality and security of newly developed C language code while eliminating obstacles to widespread adoption and possible Wiki MarkupThe managed string library described in \[[Burch 06|AA. References#Burch06]\] was developed in response to the need for a string library that could improve the quality and security of newly developed C language code while eliminating obstacles to widespread adoption and possible standardization.

The managed string library is based on a dynamic approach in which memory is allocated and reallocated as required. This approach eliminates the possibility of unbounded copies, null-termination errors, and truncation by ensuring there adequate space is always adequate space available for the resulting string (including the terminating null character).

A runtime-constraint violation occurs when memory cannot be allocated. In this way, the managed string library accomplishes the goal of succeeding or failing in accomplishes success or failure in a pronounced manner.

The managed string library also provides a mechanism for dealing with data sanitization by (optionally) checking that all characters in a string belong to a predefined set of safe characters.

The following code shows how the managed string library can be used to create a managed string and retrieve a null-terminated byte string from the managed string.:

errno_t retValue;
char *cstr;  /* pointerPointer to null-terminated byte string */
string_mx *str1 = NULL;

retValue = strcreate_m(&str1, "hello, world", 0, NULL);
if (retValue != 0) {
  fprintf(stderr, "Error %d from strcreate_m.\n", retValue);
}
else { /* retrieveRetrieve null-terminated byte string and print */
  retValue = getstr_m(&cstr, str1);
  if (retValue != 0) {
    fprintf(stderr, "error %d from getstr_m.\n", retValue);
  }
  printf("(%s)\n", cstr);
  free(cstr); /* freeFree null-terminated byte string */
  cstr = NULL;
}

...

Note that the calls to {{fprintf()}} and {{printf()}} are C99 \[[ISO/IEC 9899:1999|AA. References#ISO/IEC 9899-1999]\] standard functions and not managed string are C Standard functions and not managed string functions.

The forthcoming technical report ISO/IEC TR 24731-2 [ISO/IEC TR 24731-2 will :2010] also provide provides an API that dynamically allocates the results of string functions as needed.

Risk Assessment

Wiki MarkupString handling functions defined in C99 \[[ISO/IEC 9899:1999|AA. References#ISO/IEC 9899-1999]\] Section 7.21 and elsewhere are susceptible to common programming errors that can lead to serious, exploitable [vulnerabilities|BB. Definitions#vulnerability]. Managed strings, when used properly, can eliminate many of these errors, particularly in new String-handling functions defined in the C Standard, subclause 7.24, and elsewhere are susceptible to common programming errors that can lead to serious, exploitable vulnerabilities. Managed strings, when used properly, can eliminate many of these errors, particularly in new development.

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

References

\[[Burch 06|AA. References#Burch06]\]
\[[CERT 06c|AA. References#CERT 06c]\]
\[[ISO/IEC 9899:1999|AA. References#ISO/IEC 9899-1999]\] Section 7.21, "String handling <{{string.h}}>"
\[[Seacord 05a|AA. References#Seacord 05a]\] Chapter 2, "Strings"

Bibliography

...

Image Added Image Added STR07-C. Use TR 24731 for remediation of existing string manipulation code      07. Characters and Strings (STR)      Image Modified