This vulnerability occurs when an application fails to properly remove temporary files, data structures, or system resources after they are no longer needed.
Incomplete cleanup happens when developers focus on the primary function of their code but neglect the final 'housekeeping' steps. This often involves forgetting to close file handles, database connections, or network sockets, or leaving temporary files in shared directories. These leftover resources can accumulate over time, leading to performance degradation, data leaks, or denial of service as system limits are reached. From a security perspective, uncleaned temporary files can expose sensitive data to other users or processes on the system. In multi-user environments, this can allow unauthorized access to session tokens, configuration secrets, or user data. The risk is particularly high when predictable filenames are used, as attackers can easily locate and exploit these residual artifacts.
Impact: OtherRead Application DataModify Application DataDoS: Resource Consumption (Other)
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.
java