JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
A value that may have network taint is used to set an environment variable.
| Class Name | Tainted Environment Variable | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Significance | security | ||||||||||||
| Mnemonic | IO.TAINT.ENV | ||||||||||||
| Categories |
|
||||||||||||
| Availability | Available for C and C++. |
||||||||||||
| Enabling | Checks for this warning class are enabled by
default. To disable them, add the following WARNING_FILTER rule to the
project configuration file.
WARNING_FILTER += discard class="Tainted Environment Variable" |
Japanese (ja)
#include <stdlib.h>
#include <sys/socket.h>
int io_taint_env(int sock){
char val[16];
if (recv(sock, val, 16, 0) <= 0 ) return -1;
return putenv(val); /* 'Tainted Environment Variable' warning issued here */
}
CodeSonar ships with library models that allow it to recognize functions such as libc setenv() and Win32 _putenv() that use one or more of their parameters to set an environment variable. If one of these functions is called with a potentially-network-tainted value in the variable name or value parameter position, a warning will be issued.
If you have created a custom library model for some function f() in terms of one of these existing models, calls to f() will also be capable of triggering Tainted Environment Variable warnings.
The following configuration file parameters affect checks for this warning class.