CWE一覧に戻る
CWE-779

過剰データのログ記録

Logging of Excessive Data
脆弱性 レビュー中
JA

この製品ではログに記録される情報が多すぎるため、ログファイルの処理が困難になり、攻撃後の復旧作業やフォレンジック分析の妨げになる可能性がある。

一般的にロギングは良い習慣であり、開発のデバッグ段階では非常に高いレベルのロギングが適切ですが、実運用環境での多すぎるロギングは、システム管理者が異常な状態を検出する能力を妨げるかもしれません。これは、システムへの侵入を試みる攻撃者に隠れ蓑を提供し、フォレンジック分析のための監査証跡を乱雑にし、あるいは、本番環境での問題のデバッグをより困難にする可能性があります。

EN

The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.

While logging is a good practice in general, and very high levels of logging are appropriate for debugging stages of development, too much logging in a production environment might hinder a system administrator's ability to detect anomalous conditions. This can provide cover for an attacker while attempting to penetrate a system, clutter the audit trail for forensic analysis, or make it more difficult to debug problems in a production environment.

Scope: Availability / Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other)
Scope: Non-Repudiation / Impact: Hide Activities
Scope: Non-Repudiation / Impact: Hide Activities
Suppress large numbers of duplicate log messages and replace them with periodic summaries. For example, syslog may include an entry that states "last message repeated X times" when recording repeated events.
Support a maximum size for the log file that can be controlled by the administrator. If the maximum size is reached, the admin should be notified. Also, consider reducing functionality of the product. This may result in a denial-of-service to legitimate product users, but it will prevent the product from adversely impacting the entire system.
Adjust configurations appropriately when the product is transitioned from a debug state to production.
MITRE公式ページ — CWE-779