CWE-1325 - Improperly Controlled Sequential Memory Allocation
CWE-1325
- Abstraction:
- Base
- Structure:
- Simple
- Status:
- Incomplete
- Weakness Name
Improperly Controlled Sequential Memory Allocation
- Description
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
While the product might limit the amount of memory that is allocated in a single operation for a single object (such as a malloc of an array), if an attacker can cause multiple objects to be allocated in separate operations, then this might cause higher total memory consumption than the developer intended, leading to a denial of service.
- Common Consequences
Scope: Availability
Impact: DoS: Resource Consumption (Memory)
Notes: Not controlling memory allocation can result in a request for too much system memory, possibly leading to a crash of the application due to out-of-memory conditions, or the consumption of a large amount of memory on the system.
- Related Weaknesses
- Release Date:
- 2020-12-10
- Latest Modification Date:
- 2023-06-29
Free security scan for your website