The getenv()
function searches an environment list for a string that matches a specified name and returns a pointer to a string associated with the matched list member.
Subclause 7.22.4.6 of the C Standard [ISO/IEC 9899:2011] states: Section 7.20.4.5 of C99 says that \[[ISO/IEC 9899-1999|AA. C References#ISO/IEC 9899-1999]\] Wiki Markup
The set of environment names and the method for altering the environment list are implementation-defined.
The getenv()
function searches an environment list for a string that matches a specified name, and returns a pointer to a string associated with the matched list member. Depending on the implementation, multiple environment variables with the same name may be allowed and can cause unexpected results if a program cannot consistently choose the same value. The GNU glibc library addresses this issue in getenv()
and setenv()
by always using the first variable it encounters and ignoring the rest. Other implementations are following suitHowever, although it is unwise to rely on this behavior.
One common difference between implementations is whether or not environment variables are case sensitive. While Although UNIX-like implementations are generally case sensitive, environment variables are "not case sensitive in Windows 98/Me and Windows NT/2000/XP" . \ [[MSDN|AA. C References#MSDN]\]]. Wiki Markup
Duplicate Environment Variable Detection (POSIX)
Here is The following code defines a function that uses the POSIX environ
array (specified in POSIX) to manually search for duplicate key entries. Any duplicate environment variables are considered an attack, and so the program immediately terminates if a duplicate is detected.
Code Block | ||||
---|---|---|---|---|
| ||||
extern char ** environ; int main(void) { if (multiple_vars_with_same_name()) { printf("Someone may be tampering.\n"); return 1; } /* ... */ return 0; } int multiple_vars_with_same_name(void) { size_t i; size_t j; size_t k; size_t l; size_t len_i; size_t len_j; for(size_t i = 0; environ[i] != NULL; i++) { for(size_t j = i; environ[j] != NULL; j++) { if (i != j) { k = 0; l = 0; len_i = strlen(environ[i]); len_j = strlen(environ[j]); while (k < len_i && l < len_j) { if (environ[i][k] != environ[j][l]) break; if (environ[i][k] == '=') return 1; k++; l++; } } } } return 0; } |
...
Noncompliant Code Example
This noncompliant code example behaves differently when compiled under and run on Linux and Microsoft Windows .platforms:
Code Block | ||||
---|---|---|---|---|
| ||||
char *temp; if (putenv("TEST_ENV=foo") != 0) { /* Handle Errorerror */ } if (putenv("Test_ENV=bar") != 0) { /* Handle Errorerror */ } const char *temp = getenv("TEST_ENV"); if (temp == NULL) { /* Handle Errorerror */ } printf("%s\n", temp); |
On a test an IA-32 Linux machine with GCC Compiler Version 3.4.4, this code prints:
Code Block |
---|
foo
|
Whereaswhereas, on a test an IA-32 Windows XP machine with Microsoft Visual C++ 2008 Express, it prints:
Code Block |
---|
bar
|
Compliant Solution
Portable code should use environment variables that differ by more than capitalization.:
Code Block | ||||
---|---|---|---|---|
| ||||
char *temp; if (putenv("TEST_ENV_1=foo") != 0) { /* Handle Errorerror */ } if (putenv("TESTOTHER_ENV_2=bar") != 0) { /* Handle Errorerror */ } const char *temp = getenv("TEST_ENV"); if (temp == NULL) { /* Handle Errorerror */ } printf("%s\n", temp); |
Risk Assessment
An adversary attacker can create multiple environment variables with the same name (for example, by using the POSIX execve()
function). If the program checks one copy but uses another, security checks may be circumvented.
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
ENV02- |
medium
unlikely
low
P6
C | Low | Unlikely | Medium | P2 | L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Compass/ROSE | |||||||||
Parasoft C/C++test |
| CERT_C-ENV02-a | Usage of system properties (environment variables) should be restricted |
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]\] Section 7.20.4, "Communication with the environment"
\[[MSDN|AA. C References#MSDN]\] [{{getenv()}}|http://msdn.microsoft.com/en-us/library/tehxacec(VS.71).aspx] |
Related Guidelines
SEI CERT C++ Coding Standard | VOID ENV00-CPP. Beware of multiple environment variables with the same effective name |
ISO/IEC TR 24772:2013 | Executing or Loading Untrusted Code [XYS] |
MITRE CWE | CWE-462, Duplicate key in associative list (Alist) CWE-807, Reliance on untrusted inputs in a security decision |
Bibliography
[ISO/IEC 9899:2011] | Section 7.22.4, "Communication with the Environment" |
[MSDN] | getenv() |
...
ENV01-A. Do not make assumptions about the size of an environment variable 10. Environment (ENV) ENV03-A. Sanitize the environment when invoking external programs