Read Time:1 Minute, 49 Second
Description
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.
Modes of Introduction:
– Operation
Likelihood of Exploit: Low
Related Weaknesses
CWE-400
Consequences
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 diagnose a problem or recover from an attack.
Non-Repudiation: Hide Activities
If system administrators are unable to effectively process log files, attempted attacks may go undetected, possibly leading to eventual system compromise.
Potential Mitigations
Phase: Architecture and Design
Effectiveness:
Description:
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.
Phase: Architecture and Design
Effectiveness:
Description:
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.
Phase: Implementation
Effectiveness:
Description:
Adjust configurations appropriately when software is transitioned from a debug state to production.
CVE References
- 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
