CWE一覧に戻る
CWE-215

デバッグ・コードへの機密情報の挿入

Insertion of Sensitive Information Into Debugging Code
脆弱性 レビュー中
JA

本製品はデバッグコードに機密情報を挿入するため、本番環境でデバッグコードが無効化されていない場合、この情報が漏洩する可能性がある。

デバッグ時には、プログラマーに詳細な情報を報告する必要があるかもしれない。 しかし、製品が本番環境で動作しているときにデバッグ・コードが無効になっていなければ、この機密情報が攻撃者にさらされる可能性がある。

EN

The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.

When debugging, it may be necessary to report detailed information to the programmer. However, if the debugging code is not disabled when the product is operating in a production environment, then this sensitive information may be exposed to attackers.

Scope: Confidentiality / Impact: Read Application Data
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
MITRE公式ページ — CWE-215