Statements (34)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:Common_Weakness_Enumeration
|
| gptkbp:bfsLayer |
6
|
| gptkbp:bfsParent |
gptkb:CWE-23
|
| gptkbp:category |
Resource Management Errors
|
| gptkbp:consequences |
Decreased performance over time.
Increased operational costs due to resource consumption. |
| gptkbp:difficulty |
gptkb:High
|
| gptkbp:example |
A program that allocates memory for an object but does not free it after use.
|
| gptkbp:has_weakness |
gptkb:CWE-590
CWE-682 |
| https://www.w3.org/2000/01/rdf-schema#label |
CWE-865
|
| gptkbp:impact |
Memory leaks can lead to increased memory usage.
Potential application crashes due to exhaustion of memory. |
| gptkbp:is_described_as |
The software does not release memory that is no longer needed.
|
| gptkbp:is_protected_by |
Adopt garbage collection in managed languages.
Implement proper memory management practices. Use automated tools to detect memory leaks. Use smart pointers in C++. Regularly review and test code for memory management issues. |
| gptkbp:is_vulnerable_to |
A web server that allocates memory for each request but does not release it.
|
| gptkbp:language |
C, C++, Java
|
| gptkbp:name |
Missing Release of Memory
|
| gptkbp:related_to |
gptkb:CWE-119
gptkb:CWE-590 gptkb:CWE-787 gptkb:CWE-835 gptkb:CWE-125 CWE-476 CWE-401 CWE-416 CWE-682 CWE-772 CWE-824 CWE-843 |