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
C and C++
Binaries

IO.TAINT.WRITE : 汚染された書き込み

要旨

汚染された可能性のある値が、ファイルもしくは他の出力に書き込まれました。

プロパティ

クラス名 Tainted Write
日本語クラス名 汚染された書き込み
クラス分類 セキュリティ (security)
ニーモニック IO.TAINT.WRITE
カテゴリー
MisraC2025 MisraC2025:D.4.14 The validity of values received from external sources shall be checked
MisraC2023 MisraC2023:D.4.14 The validity of values received from external sources shall be checked
Misra2012 Misra2012:D.4.14 The validity of values received from external sources shall be checked
AUTOSARC++14 AUTOSARC++14:A27-0-1 Inputs from independent components shall be validated.
MisraC++2023 MisraC++2023:0.3.2 A function call shall not violate the function's preconditions
CWE CWE:200 Exposure of Sensitive Information to an Unauthorized Actor
TS17961 TS17961:5.39-taintformatio Using a tainted value to write to an object using a formatted input or output function
DISA-6r1 DISA-6r1:V-222606 The application must validate all input.
  DISA-6r1:V-222609 The application must not be subject to input handling vulnerabilities.
DISA-5r3 DISA-5r3:V-70265 The application must validate all input.
  DISA-5r3:V-70271 The application must not be subject to input handling vulnerabilities.
DISA-4r3 DISA-4r3:V-70265 The application must validate all input.
  DISA-4r3:V-70271 The application must not be subject to input handling vulnerabilities.
DISA-3r10 DISA-3r10:V-6164 The designer will ensure the application validates all input.
OWASP-2017 OWASP-2017:A1 Injection
  OWASP-2017:A3 Sensitive data exposure
  OWASP-2017:A5 Broken access control
  OWASP-2017:A7 Cross site scripting (XSS)
OWASP-2021 OWASP-2021:A1 Broken access control
  OWASP-2021:A2 Cryptographic failures
  OWASP-2021:A3 Injection
OWASP-2025 OWASP-2025:A01 Broken Access Control
  OWASP-2025:A05 Injection
対応言語 C および C++ で利用可能です。
有効/無効設定 このワーニングクラスのチェックはデフォルトで無効になっています。チェックを有効にするにはプロジェクト設定ファイル （configuration file）に以下の WARNING_FILTER ルールを追加してください。 
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 a large number of functions that write one of their arguments to a file or other output. 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()

関連のある設定ファイルパラメータ

設定ファイルの以下のパラメータがこのワーニングクラスのチェックに影響します。

 

To report problems with this documentation, please visit https://support.codesecure.com/.