Nama: 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.

Informasi Umum

Mode Pengenalan

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

Platform yang Berlaku

Bahasa

Kelas: Not Language-Specific (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Availability	DoS: Resource Consumption (CPU), DoS: Resource Consumption (Other) Catatan: 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 Catatan: Logging too much information can make the log files of less use to forensics analysts and developers when trying to detect anomalous conditions, diagnose a problem, or recover from an attack. This can provide cover for an attacker while attempting to penetrate a system. If system administrators are unable to effectively process log files, attempted attacks may go undetected, possibly leading to eventual system compromise.

Contoh yang Diamati

Referensi	Deskripsi
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

Mitigasi yang Memungkinkan

Phases : 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.
Phases : 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.
Phases : Implementation
Adjust configurations appropriately when the product is transitioned from a debug state to production.

Metode Deteksi

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

Catatan Pemetaan Kerentanan

Justifikasi : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
CWE Content Team	MITRE	2009-07-02 +00:00	2009-07-27 +00:00	1.5

Modifikasi

Nama	Organisasi	Tanggal	Komentar
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2017-11-08 +00:00	updated Likelihood_of_Exploit, Modes_of_Introduction, Relationships
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description, Potential_Mitigations
CWE Content Team	MITRE	2023-04-27 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2025-12-11 +00:00	updated Detection_Factors, Weakness_Ordinalities
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description, Dimensions

Detail CWE-779

CWE-779