Logging of Excessive Data

Opis

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.

Skutki

• 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.

Zapobieganie

• 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 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.

• Implementation

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

Przykłady podatności

• 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

Słabość nadrzędna

• CWE-400 Uncontrolled Resource Consumption

Kiedy powstaje

• Operation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific