Allocation of File Descriptors or Handles Without Limits or Throttling

Opis

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.

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

Inne nazwy

File Descriptor Exhaustion

Skutki

• Availability

  DoS: Resource Consumption (Other)

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

Zapobieganie

• Operation, Architecture and Design · Resource Limitation

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

Słabość nadrzędna

• CWE-770 Allocation of Resources Without Limits or Throttling

Kiedy powstaje

• Architecture and Design
• Implementation

Dotyczy

Not Language-Specific

Źródła

1. The Art of Software Security Assessment — Mark Dowd, John McDonald, Justin Schuh, Chapter 10, "Resource Limits", Page 574, Addison Wesley, 2006