The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.
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.
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.
Adjust configurations appropriately when the product is transitioned from a debug state to production.
Our security experts can help you identify and remediate CWE-779 vulnerabilities in your codebase.
Get Security Assessment