CWE-779 日志记录过多数据

Logging of Excessive Data

结构: Simple

Abstraction: Base

状态: Draft

被利用可能性: Low

基本描述

The software 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.

相关缺陷

• cwe_Nature: ChildOf cwe_CWE_ID: 400 cwe_View_ID: 1000 cwe_Ordinal: Primary

• cwe_Nature: ChildOf cwe_CWE_ID: 400 cwe_View_ID: 699 cwe_Ordinal: Primary

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

常见的影响

可能的缓解方案

Architecture and Design

策略:

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.

Architecture and Design

策略:

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 software. This may result in a denial-of-service to legitimate software users, but it will prevent the software from adversely impacting the entire system.

Implementation

策略:

Adjust configurations appropriately when software is transitioned from a debug state to production.

分析过的案例

文章来源于互联网:scap中文网