名称: Logging of Excessive Data
The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.
基本信息
引入方式
Operation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.适用平台
编程语言
类： Not Language-Specific (Undetermined)常见后果
| 影响范围 | 影响 | 可能性 |
|---|---|---|
| Availability | DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other) 注意： Log files can become so large that they consume excessive resources, such as disk and CPU, which can hinder the performance of the system. | |
| Non-Repudiation | Hide Activities 注意： Logging too much information can make the log files of less use to forensics analysts and developers when trying to detect anomalous conditions, diagnose a problem, or recover from an attack. This can provide cover for an attacker while attempting to penetrate a system. If system administrators are unable to effectively process log files, attempted attacks may go undetected, possibly leading to eventual system compromise. |
观察示例
| 参考资料 | 描述 |
|---|---|
CVE-2007-0421 | server records a large amount of data to the server log when it receives malformed headers |
CVE-2002-1154 | Chain: application does not restrict access to front-end for updates, which allows attacker to fill the error log |
潜在缓解措施
Phases : Architecture and DesignSuppress 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.
Phases : 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 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.
Phases : Implementation
Adjust configurations appropriately when the product is transitioned from a debug state to production.
检测方法
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)漏洞映射说明
依据 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.备注 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
提交记录
| 名称 | 组织 | 日期 | 发布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.5 |
修改记录
| 名称 | 组织 | 日期 | 备注 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Likelihood_of_Exploit, Modes_of_Introduction, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description, Potential_Mitigations | |
| CWE Content Team | MITRE | updated Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Detection_Factors, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Dimensions |
