Some functions return a pointer to an object that cannot be modified without causing undefined behavior. These functions include the standard getenv()
, setlocale()
, localeconv()
, and strerror()
functions.
Section 7.22.4.6 of the C standard [ISO/IEC 9899:2011] defines getenv
as follows:
The
getenv
function returns a pointer to a string associated with the matched list member. The string pointed to shall not be modified by the program, but may be overwritten by a subsequent call to thegetenv
function. If the specified name cannot be found, a null pointer is returned.
Consequently, if the string returned by getenv()
must be altered, a local copy should be created. Altering the string returned by getenv()
results in undefined behavior. See also undefined behavior 184 of Annex J of C11.
Similarly, Section 7.11.1.1 [ISO/IEC 9899:2011] defines setlocale
and localeconv
as follows:
The pointer to string returned by the
setlocale
function is such that a subsequent call with that string value and its associated category will restore that part of the program's locale. The string pointed to shall not be modified by the program, but may be overwritten by a subsequent call to thesetlocale
function.
The
localeconv
function returns a pointer to the filled-in object. The structure pointed to by the return value shall not be modified by the program, but may be overwritten by a subsequent call to thelocaleconv
function.
Altering the string returned by setlocale()
or the structure returned by localeconv()
results in undefined behavior. See also undefined behaviors 120 and 121 of Annex J. Furthermore, the C standard imposes no requirements on the contents of the string by setlocale()
. Consequently, a program should make no assumptions as to the string's internal contents or structure.
Finally, Section 7.24.6.2 [ISO/IEC 9899:2011], states:
The
strerror
function returns a pointer to the string, the contents of which are locale specific. The array pointed to shall not be modified by the program, but may be overwritten by a subsequent call to thestrerror
function.
Altering the string returned by strerror()
results in undefined behavior. See also undefined behavior 184 of Annex J.
Noncompliant Code Example (getenv()
)
This noncompliant code example modifies the string returned by getenv()
by replacing all double quote ("
) characters with underscores.
void trstr(char *str, char orig, char rep) { while (*str != '\0') { if (*str == orig) { *str = rep; } str++; } } /* ... */ char *env = getenv("TEST_ENV"); if (env == NULL) { /* Handle error */ } trstr(env,'"', '_'); /* ... */
Compliant Solution (getenv()
) (Local Copy)
If the intent of the noncompliant code example is to use the modified value of the environment variable locally and not modify the environment, this compliant solution makes a local copy of that string value and then modifies it.
const char *env; char *copy_of_env; env = getenv("TEST_ENV"); if (env == NULL) { /* Handle error */ } copy_of_env = (char *)malloc(strlen(env) + 1); if (copy_of_env == NULL) { /* Handle error */ } strcpy(copy_of_env, env); trstr(copy_of_env,'\"', '_');
Compliant Solution (getenv()
) (Modifying the Environment in POSIX)
If the intent is to modify the environment, this compliant solution saves the altered string back into the environment by using the POSIX setenv()
and strdup()
functions.
const char *env; char *copy_of_env; env = getenv("TEST_ENV"); if (env == NULL) { /* Handle error */ } copy_of_env = strdup(env); if (copy_of_env == NULL) { /* Handle error */ } trstr(copy_of_env,'\"', '_'); if (setenv("TEST_ENV", copy_of_env, 1) != 0) { /* Handle error */ }
Noncompliant Code Example (localeconv()
)
In this noncompliant example, the object returned from the C Standard Library function localeconv()
is modified.
void f2(void) { struct lconv *conv = localeconv(); if ('\0' == conv->decimal_point[0]) { conv->decimal_point = "."; /* violation */ } if ('\0' == conv->thousands_sep[0]) { conv->thousands_sep = ","; /* violation */ } /* ... */ }
Compliant Solution (localeconv()
) (Local Copy)
This compliant solution makes a local copy of the object and then modifies it.
void f2(void) { struct lconv *conv = localeconv(); if (conv == NULL) { /* Handle error */ } copy_of_conv = (char *)malloc(sizeof(lconv) + 1); if (copy_of_conv == NULL) { /* Handle error */ } memcpy(copy_of_conv, conv, sizeof(lconv)); if ('\0' == copy_of_conv->decimal_point[0]) { copy_of_conv->decimal_point = "."; } if ('\0' == copy_of_conv->thousands_sep[0]) { copy_of_conv->thousands_sep = ","; } /* ... */ }
Risk Assessment
Depending on the implementation, modifying the object pointed to by the return value of these functions causes undefined behavior. Even if the modification succeeds, the modified object can be overwritten by a subsequent call to the getenv()
, setlocale()
, localeconv()
, or strerror()
functions.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
ENV30-C | low | probable | medium | P4 | L3 |
Automated Detection
Tool | Version | Checker | Description |
---|---|---|---|
Compass/ROSE | Can detect violations of this rule. In particular, it ensures that the result of |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
CERT C++ Secure Coding Standard: ENV30-CPP. Do not modify the string returned by getenv()
ISO/IEC 9899:2011 Section 7.11.1.1, "The setlocale
function," Section 7.11.2.1, "The localeconv
function," Section 7.22.4.6, "The getenv
function," and Section 7.24.6.2, "The strerror
function"
ISO/IEC TR 17961 (Draft) Modifying the string returned by getenv, localeconv, setlocale, and strerror [libmod]
Bibliography
[Open Group 2004] getenv, setlocale, localeconv