CWE-1341: Multiple Releases of Same Resource or Handle

Description:
The product attempts to close or release a resource or handle more than once, without any successful open between the close operations.

Extended Description:
Code typically requires "opening" handles or references to resources such as memory, files, devices, socket connections, services, etc. When the code is finished with using the resource, it is typically expected to "close" or "release" the resource, which indicates to the environment (such as the OS) that the resource can be re-assigned or reused by unrelated processes or actors - or in some cases, within the same process. API functions or other abstractions are often used to perform this release, such as free() or delete() within C/C++, or file-handle close() operations that are used in many languages. 
			   Unfortunately, the implementation or design of such APIs might expect the developer to be responsible for ensuring that such APIs are only called once per release of the resource. If the developer attempts to release the same resource/handle more than once, then the API's expectations are not met, resulting in undefined and/or insecure behavior. This could lead to consequences su

Affected languages: Java, Rust, Not Language-Specific, C, C++
Affected technologies: Not Technology-Specific
Parent weaknesses: CWE-675

Consequences:
  - Availability: DoS: Crash, Exit, or Restart

Detection methods:
  - Automated Static Analysis: For commonly-used APIs and resource types, automated tools often have signatures that can spot this issue.
  - Automated Dynamic Analysis: Some compiler instrumentation tools such as AddressSanitizer (ASan) can indirectly detect some instances of this weakness.

Mitigations:
  - [Implementation] Change the code's logic so that the resource is only closed once. This might require simplifying or refactoring. This fix can be simple to do in small code blocks, but more difficult when multiple closes are buried within complex conditionals.
  - [Implementation] It can be effective to implement a flag that is (1) set when the resource is opened, (2) cleared when it is closed, and (3) checked before closing. This approach can be useful when there are disparate cases in which closes must be performed. However, flag-tracking can increase code complexity and re
  - [Implementation] When closing a resource, set the resource's associated variable to NULL or equivalent value for the given language. Some APIs will ignore this null value without causing errors. For other APIs, this can lead to application crashes or exceptions, which may still be preferable to corrupting an uninten

Demonstrative examples:
This example attempts to close a file twice. In some cases, the C library fclose() function will catch the error and return an error code. In other implementations, a double-free (CWE-415) occurs, causing the program to fault. Note that the examples presented here are simplistic, and double fclose() calls will frequently be spread around a program, making them more difficult to find during code reviews.
There are multiple possible fixes. This fix only has one call to fclose(), which is typically the preferred handling of this problem - but this simplistic method is not always possible.
char b[2000]; 
FILE *f = fopen("dbl_cls.c", "r"); 
if (f) 
{ 
	 b[0] = 0; 
	fread(b, 1, sizeof(b) - 1, f); 
	printf("%s\n'", b); 
	int r1 = fclose(f); 
	printf("\n-----------------\n1 close done '%d'\n", r1)

The following code shows a simple example of a double free vulnerability.
Double free vulnerabilities have two common (and sometimes overlapping) causes:
char* ptr = (char*)malloc (SIZE); ... if (abrt) { free(ptr); } ... free(ptr);

Real-world examples:
  - CVE-2019-13351: file descriptor double close can cause the wrong file to be associated with a file descriptor.
  - CVE-2006-5051: Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).
  - CVE-2004-0772: Double free resultant from certain error conditions.