Allocation of File Descriptors or Handles Without Limits or Throttling

The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor.

Soyutlama

Variant

Yapı

Simple

Sömürü İhtimali

Low

Problemi anla

Problem nedir?

Genişletilmiş açıklama

This can cause the product to consume all available file descriptors or handles, which can prevent other processes from performing critical file processing operations.

Terminoloji

Alternatif adlar ve kullanım biçimleri

File Descriptor Exhaustion

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Architecture and Design

Yaşam döngüsü evresi

Implementation

Risk

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

DoS: Resource Consumption (Other)

Etkilenen güvenlik alanları: Availability

When allocating resources without limits, an attacker could prevent all other processes from accessing the same type of resource.

Savunma

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

Operation · Architecture and Design

Resource Limitation

Detay

Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems. When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users. Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

Doğrulama

Nasıl tespit edilir?

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