Allocation of File Descriptors or Handles Without Limits or Throttling

Incomplete Variant
Structure: Simple
Description

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.

Extended Description

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

Common Consequences 1
Scope: Availability

Impact: DoS: Resource Consumption (Other)

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

Potential Mitigations 1
Phase: OperationArchitecture and Design

Strategy: 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 Allocation of Resources Without Limits or Throttling), 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 (Improper Check or Handling of Exceptional Conditions).
References 1
The Art of Software Security Assessment
Mark Dowd, John McDonald, and Justin Schuh
Addison Wesley
2006
ID: REF-62
Likelihood of Exploit

Low

Modes of Introduction
Architecture and Design
Implementation
Alternate Terms

File Descriptor Exhaustion

Taxonomy Mapping
  • Software Fault Patterns