CWE-404
Improper Resource Shutdown or Release
AI Translation Available
The product does not release or incorrectly releases a resource before it is made available for re-use.
Status
draft
Abstraction
class
Likelihood
medium
Affected Platforms
Extended Description
AI Translation
When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation, such as a set period of time or revocation.
Technical Details
AI Translation
Common Consequences
availability
other
confidentiality
Impacts
dos: resource consumption (other)
varies by context
read application data
Detection Methods
automated dynamic analysis
manual dynamic analysis
automated static analysis
Potential Mitigations
Phases:
requirements
implementation
Descriptions:
•
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
•
Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
•
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error conditions.
•
When releasing a complex object or structure, ensure that you properly dispose of all of its member components, not just the object itself.