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.2p0 | CONFIDENTIAL | CodeSecure Inc |
A potentially-tainted value is written to a file or other output.
| Class Name | Tainted Write | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Significance | security | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Mnemonic | IO.TAINT.WRITE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Categories |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Availability | Available for C and C++. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Enabling | Checks for this warning class are
disabled by default. To enable them, add the following WARNING_FILTER
rule to the project configuration file.
WARNING_FILTER += allow class="Tainted Write" |
#include <stdio.h>
void do_tainted_write(FILE * src, FILE * dest)
{
putc (getc(src), dest); /* 'Tainted Write' warning issued here */
}
CodeSonar ships with library models that allow it to recognize a large number of functions that write one of their arguments to a file or other output. Some examples are shown in the table below. If one of these functions is called with a potentially-tainted value in the output 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 Write warnings.
| Functions that can trigger a warning include... | |
|---|---|
| gcc Builtins | __builtin___fprintf_chk(), __builtin_puts() |
| libc | fprintf(), pwrite(), sendmsg() |
| Win32 | fprintf_s(), putwchar(), _write() |
The following configuration file parameters affect checks for this warning class.
To report problems with this documentation, please visit https://support.codesecure.com/.