Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1325 CNY

100%
Buy Us a Coffee

CWE-404 (不恰当的资源关闭或释放) — Vulnerability Class 360

360 vulnerabilities classified as CWE-404 (不恰当的资源关闭或释放). AI Chinese analysis included.

CWE-404 represents a critical resource management weakness where software fails to properly release or incorrectly frees allocated resources, such as memory, file handles, or network connections, before they are reused. This flaw typically leads to resource exhaustion, causing application crashes, denial of service, or system instability as available resources dwindle. Attackers often exploit this by triggering repeated allocations without corresponding releases, effectively starving the system of necessary assets. To mitigate this risk, developers must implement rigorous lifecycle management, ensuring every allocated resource has a corresponding release mechanism. This involves using structured cleanup routines, leveraging language-specific garbage collection or smart pointers, and accounting for all execution paths, including error conditions and timeouts, to guarantee resources are consistently returned to the pool for safe reuse.

MITRE CWE Description
The product does not release or incorrectly releases a resource before it is made available for re-use. 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.
Common Consequences (2)
Availability, OtherDoS: Resource Consumption (Other), Varies by Context
Most unreleased resource issues result in general software reliability problems, but if an attacker can intentionally trigger a resource leak, the attacker might be able to launch a denial of service attack by depleting the resource pool.
ConfidentialityRead Application Data
When a resource containing sensitive information is not correctly shutdown, it may expose the sensitive data in a subsequent allocation.
Mitigations (4)
RequirementsUse 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.
ImplementationIt 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.
ImplementationMemory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
ImplementationWhen releasing a complex object or structure, ensure that you properly dispose of all of its member components, not just the object itself.
Examples (2)
The following method never closes the new file handle. Given enough time, the Finalize() method for BufferReader should eventually call Close(), but there is no guarantee as to how long this action will take. In fact, there is no guarantee that Finalize() will ever be invoked. In a busy environment, the Operating System could use up all of the available file handles before the Close() function is …
private void processFile(string fName) { BufferReader fil = new BufferReader(new FileReader(fName)); String line; while ((line = fil.ReadLine()) != null) { processLine(line); } }
Bad · Java
private void processFile(string fName) { BufferReader fil = new BufferReader(new FileReader(fName)); String line; while ((line = fil.ReadLine()) != null) { processLine(line); } fil.Close(); }
Good · Java
This code attempts to open a connection to a database and catches any exceptions that may occur.
try { Connection con = DriverManager.getConnection(some_connection_string); } catch ( Exception e ) { log( e ); }
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2026-11317 Rockwell Automation Logix 5370 and 5570 Controllers Vulnerable To Denial of Service Via CIP — CompactLogix, ControlLogix--2026-06-16
CVE-2026-45174 Idira Endpoint Privilege Manager Linux Agent: Potential bypass of Agent Daemon Initialization — Idira Endpoint Privilege Manager--2026-06-11
CVE-2026-47213 BoxLite: Timeout Bypass Vulnerability — boxlite 6.5 Medium2026-06-10
CVE-2026-10775 sgl-project SGLang Cache data_hash denial of service — SGLang 3.6 Low2026-06-03
CVE-2026-10295 SourceCodester Customer Review App review_app.py get_all_reviews denial of service — Customer Review App 3.3 Low2026-06-01
CVE-2026-10190 Tenda W12 Web Management httpd cgiSysWebTimeoutSet denial of service — W12 6.5 Medium2026-05-31
CVE-2026-10117 Open5GS nghttp2-server.c ogs_pool_id_calloc denial of service — Open5GS 4.3 Medium2026-05-30
CVE-2026-10116 Open5GS ue-authentications Endpoint ogs-timer.c ogs_sbi_xact_add denial of service — Open5GS 4.3 Medium2026-05-30
CVE-2026-10115 Open5GS Shared NF-profile nnrf-handler.c denial of service — Open5GS 4.3 Medium2026-05-30
CVE-2026-10113 Open5GS Shared NF-profile nnrf-handler.c denial of service — Open5GS 4.3 Medium2026-05-30
CVE-2026-9540 vllm-project vllm OpenAI-compatible Serving Path denial of service — vllm 5.3 Medium2026-05-26
CVE-2026-8745 Open5GS AUSF nausf-handler.c ogs_timer_add denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-8744 Open5GS NRF context.c ogs_sbi_nf_service_add denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-8731 Open5GS NRF client.c ogs_sbi_client_add denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-8730 Open5GS NRF context.c ogs_sbi_nf_instance_set_id denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-8729 Open5GS NRF message.c denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-8728 Open5GS NRF conv.c ogs_sbi_discovery_option_parse_plmn_list denial of service — Open5GS 4.3 Medium2026-05-17
CVE-2026-40136 Denial of service (DoS) in SAP Financial Consolidation — SAP Financial Consolidation 4.3 Medium2026-05-12
CVE-2026-8292 Open5GS NRF conv.c yuarel_parse denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8291 Open5GS NRF nnrf-handler.c ogs_nnrf_nfm_handle_nf_profile denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8290 Open5GS SMF nsmf-handler.c smf_nsmf_handle_update_data_in_vsmf denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8289 Open5GS SMF nsmf-handler.c smf_nsmf_handle_update_data_in_vsmf denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8288 Open5GS SMF gsm-handler.c denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8270 Open5GS SMF ogs_nas_parse_qos_rules denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8269 Open5GS SMF smf_nsmf_handle_create_sm_context denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8268 Open5GS SMF OpenAPI_list_create denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8267 Open5GS SMF smf_nsmf_handle_created_data_in_vsmf denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8266 Open5GS SMF gsm-build.c gsm_build_pdu_session_establishment_accept denial of service — Open5GS 4.3 Medium2026-05-11
CVE-2026-8251 Open5GS SMF npcf-handler.c update_authorized_pcc_rule_and_qos denial of service — Open5GS 4.3 Medium2026-05-10
CVE-2026-8250 Open5GS SMF n4-build.c smf_n4_build_qos_flow_to_modify_list denial of service — Open5GS 4.3 Medium2026-05-10

Vulnerabilities classified as CWE-404 (不恰当的资源关闭或释放) represent 360 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.