...
Code Block | ||||
---|---|---|---|---|
| ||||
#define __STDC_WANT_LIB_EXT1__ 1 #include <string.h> enum { STR_SIZE = 32 }; size_t func(const char *source) { char ac_str[STR_SIZE]; size_t ret = 0; if (source) { errno_t err = strncpy_s( ac_str, sizeof(ac_str), source, strnlen(source, sizeof(ac_str)) ); if (err != 0) { /* Handle error */ } else { ret = strnlen(c_s(astr, sizeof(ac_str)); } } else { /* Handle null pointer */ } return ret; } |
...
Code Block | ||||
---|---|---|---|---|
| ||||
#include <string.h> enum { STR_SIZE = 32 }; size_t func(const char *source) { char c_str[STR_SIZE]; size_t ret = 0; if (source) { if (strnlen(source, sizeof(c_str)) < sizeof(c_str)) { strcpy(c_str, source); ret = strlen(c_str); } else { /* Handle string-too-large */ } } else { /* Handle null pointer */ } return ret; } |
Note that this code is not bulletproof. It gracefully handles the case where source
is NULL, when it is a valid string, and when source
is not null-terminated, but at least the first 32 bytes are valid. However, in cases where source
is not NULL, but points to invalid memory, or any of the first 32 bytes are invalid memory, the first call to strnlen()
will access this invalid memory, and the resulting behavior is undefined. Unfortunately, standard C provides no way to prevent or even detect this condition without some external knowledge about the memory source
points to.
Risk Assessment
Failure to properly null-terminate a character sequence that is passed to a library function that expects a string can result in buffer overflows and the execution of arbitrary code with the permissions of the vulnerable process. Null-termination errors can also result in unintended information disclosure.
...