CWE-779: Logging of Excessive Data
low-riskThe product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.
Abstraction: Base
Common Consequences
Availability
→
DoS: Resource Consumption (CPU)
Non-Repudiation
→
Hide Activities
Non-Repudiation
→
Hide Activities
Detection Methods
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.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2024-36416 | 8.6 | 44.7% | — |
| CVE-2024-36072 | 9.8 | 6.1% | — |
| CVE-2023-23949 | 5.4 | 0.7% | — |
| CVE-2024-55628 | 7.5 | 0.5% | — |
| CVE-2025-51397 | 5.4 | 0.5% | — |
| CVE-2022-25779 | 4.3 | 0.3% | — |
| CVE-2022-31004 | 7.5 | 0.1% | — |
| CVE-2025-8696 | 7.5 | 0.1% | — |
| CVE-2026-28718 | 7.5 | 0.1% | — |
| CVE-2021-25420 | 5.5 | 0.1% | — |
2
/ 100
low-risk
Active Threat
2/50 · Minimal
Exploit Availability
0/50 · Minimal