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.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Allowed | B | 770 | Allocation of Resources Without Limits or Throttling |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 985 | SFP Secondary Cluster: Unrestricted Consumption |
| MemberOf | Prohibited | C | 1416 | Comprehensive Categorization: Resource Lifecycle Management |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-275 | Low likelihood of exploit |
| MemberOf | Prohibited | BS | BOSS-289 | Resource Limitation Strategy |
| MemberOf | Prohibited | BS | BOSS-333 | DoS: Resource Consumption (Other) (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 985 | SFP Secondary Cluster: Unrestricted Consumption |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Availability | N/A | DoS: Resource Consumption (Other) | When allocating resources without limits, an attacker could prevent all other processes from accessing the same type of resource. |
When allocating resources without limits, an attacker could prevent all other processes from accessing the same type of resource.
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).
N/A
N/A
| Reference | Description |
|---|
| Ordinality | Description |
|---|
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| Software Fault Patterns | SFP13 | N/A | Unrestricted Consumption |
| ID | Name |
|---|