Detail Latar Belakang
Mode Pengenalan
Implementation : the implementation or design of resource-management 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.
Platform yang Berlaku
Bahasa
Nama: Java (Undetermined)
Nama: Rust (Undetermined)
Kelas: Not Language-Specific (Undetermined)
Nama: C (Undetermined)
Nama: C++ (Undetermined)
Sistem Operasi
Kelas: Not OS-Specific (Undetermined)
Arsitektur
Kelas: Not Architecture-Specific (Undetermined)
Teknologi
Kelas: Not Technology-Specific (Undetermined)
Konsekuensi Umum
| Cakupan |
Dampak |
Kemungkinan |
Availability Integrity | DoS: Crash, Exit, or Restart | Medium |
| Integrity | Modify Memory, Modify Application Data
Catatan: Depending on the type of resource and the expected API behavior, this could lead to memory corruption, data corruption, or execution path corruption. | |
Contoh yang Diamati
| Referensi |
Deskripsi |
| file descriptor double close can cause the wrong file to be associated with a file descriptor. |
| Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415). |
| Double free resultant from certain error conditions. |
Mitigasi yang Memungkinkan
Phases : 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.
Phases : 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 requires diligent compliance by the programmer.
Phases : 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 unintended resource such as memory or data.
Metode Deteksi
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.
Catatan Pemetaan Kerentanan
Justifikasi : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Catatan
The terms related to "release" may vary depending on the type of resource, programming language, specification, or framework. "Close" has been used synonymously for the release of resources like file descriptors and file handles. "Return" is sometimes used instead of Release. "Free" is typically used when releasing memory or buffers back into the system for reuse.
Referensi
REF-1198
close - Perldoc Browser
https://perldoc.perl.org/functions/close REF-1199
io - Core tools for working with streams — Python 3.9.7 documentation
https://docs.python.org/3.9/library/io.html#io.IOBase.close REF-1200
FileOutputStream (Java Platform SE 7 )
https://docs.oracle.com/javase/7/docs/api/java/io/FileOutputStream.html REF-1201
FileOutputStream (Java SE 11 & JDK 11 )
https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/io/FileOutputStream.html
Pengajuan
| Nama |
Organisasi |
Tanggal |
Tanggal rilis |
Version |
| CWE Content Team |
MITRE |
2021-09-07 +00:00 |
2021-10-28 +00:00 |
4.6 |
Modifikasi
| Nama |
Organisasi |
Tanggal |
Komentar |
| CWE Content Team |
MITRE |
2022-04-28 +00:00 |
updated Demonstrative_Examples, Description, Potential_Mitigations |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated References |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Observed_Examples, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Modes_of_Introduction, References |