BaseDraft
CWE-772Missing Release of Resource after Effective Lifetime
Category: logic
Description
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Common consequences· 1
- Availability — DoS: Resource Consumption (Other), DoS: Resource Consumption (Memory), DoS: Resource Consumption (CPU)An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.
Potential mitigations· 3
- [Requirements]
- [Implementation]It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including error conditions.
- [Operation, Architecture and Design]
Related CAPEC attack patterns· 1
References
Exploits (incoming)1
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | HTTP DoScapec-469 | 100% | live |
(incoming)2
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2026-20082cve-2026-20082 | 0% | live |
| KEVEntry | Cisco ASA and FTD Denial-of-Service Vulnerabilitykev-cve-2024-20481 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.