COMMON WEAKNESS ENUMERATIONDraft

CWE-459

Incomplete Cleanup

The product does not properly "clean up" and remove temporary or supporting resources after they have been used.

Soyutlama

Base

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

The product does not properly "clean up" and remove temporary or supporting resources after they have been used.

Terminoloji

Alternatif adlar ve kullanım biçimleri

Insufficient Cleanup

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

OtherRead Application DataModify Application DataDoS: Resource Consumption (Other)

Etkilenen güvenlik alanları: Other, Confidentiality, Integrity

It is possible to overflow the number of temporary files because directories typically have limits on the number of files allowed. This could create a denial of service problem.

Savunma

Nasıl önlenir ve çözülür?

Architecture and Design · Implementation

Birden fazla yaşam döngüsü evresinde uygulanacak savunma

Detay
Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.

Doğrulama

Nasıl tespit edilir?

Automated Static Analysis

High
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.)
CWE-459: Common Weakness Enumeration Entry CWE-459 · DayBreach Sözlük · DayBreach