CWE-779: 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.

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.

Consequences

• Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other)
• Non-Repudiation: Hide Activities
• Non-Repudiation: Hide Activities

How to prevent it

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

Recent advisories

• GHSA-xp4f-g2cm-rhg7 — PocketMine-MP has LogDoS by many junk properties in client data JWT in LoginPacket
• GHSA-fh55-r93g-j68g — AIOHTTP Vulnerable to Cookie Parser Warning Storm

All advisories for CWE-779