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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

411 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, Other DoS: 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.
Confidentiality Read Application Data
When a resource containing sensitive information is not correctly shutdown, it may expose the sensitive data in a subsequent allocation.
Mitigations (4)
Requirements 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.
Implementation 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.
Implementation Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
Implementation When 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 ID Title CVSS Severity Published
CVE-2026-10113 Open5GS Shared NF-profile nnrf-handler.c denial of service — Open5GS 4.3 Medium 2026-05-30
CVE-2026-9540 vllm-project vllm OpenAI-compatible Serving Path denial of service — vllm 5.3 Medium 2026-05-26
CVE-2026-8745 Open5GS AUSF nausf-handler.c ogs_timer_add denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-8744 Open5GS NRF context.c ogs_sbi_nf_service_add denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-8731 Open5GS NRF client.c ogs_sbi_client_add denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-8730 Open5GS NRF context.c ogs_sbi_nf_instance_set_id denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-8729 Open5GS NRF message.c denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-8728 Open5GS NRF conv.c ogs_sbi_discovery_option_parse_plmn_list denial of service — Open5GS 4.3 Medium 2026-05-17
CVE-2026-40136 Denial of service (DoS) in SAP Financial Consolidation — SAP Financial Consolidation 4.3 Medium 2026-05-12
CVE-2026-8292 Open5GS NRF conv.c yuarel_parse denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8291 Open5GS NRF nnrf-handler.c ogs_nnrf_nfm_handle_nf_profile denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8290 Open5GS SMF nsmf-handler.c smf_nsmf_handle_update_data_in_vsmf denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8289 Open5GS SMF nsmf-handler.c smf_nsmf_handle_update_data_in_vsmf denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8288 Open5GS SMF gsm-handler.c denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8270 Open5GS SMF ogs_nas_parse_qos_rules denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8269 Open5GS SMF smf_nsmf_handle_create_sm_context denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8268 Open5GS SMF OpenAPI_list_create denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8267 Open5GS SMF smf_nsmf_handle_created_data_in_vsmf denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8266 Open5GS SMF gsm-build.c gsm_build_pdu_session_establishment_accept denial of service — Open5GS 4.3 Medium 2026-05-11
CVE-2026-8251 Open5GS SMF npcf-handler.c update_authorized_pcc_rule_and_qos denial of service — Open5GS 4.3 Medium 2026-05-10
CVE-2026-8250 Open5GS SMF n4-build.c smf_n4_build_qos_flow_to_modify_list denial of service — Open5GS 4.3 Medium 2026-05-10
CVE-2026-8249 Open5GS SMF npcf-handler.c update_authorized_pcc_rule_and_qos denial of service — Open5GS 4.3 Medium 2026-05-10
CVE-2026-8248 Open5GS SMF npcf-handler.c update_authorized_pcc_rule_and_qos denial of service — Open5GS 4.3 Medium 2026-05-10
CVE-2026-8232 Dotouch XproUPF UPF Process libvlib.so vlib_worker_loop denial of service — XproUPF 3.5 Low 2026-05-10
CVE-2026-7263 DoS attack via DOMNode::C14N() — PHP 7.5 - 2026-05-10
CVE-2026-8226 Open5GS types.c ogs_pcc_rule_install_flow_from_media denial of service — Open5GS 5.3 Medium 2026-05-10
CVE-2026-8225 Open5GS delete Endpoint sm-sm.c pcf_npcf_smpolicycontrol_handle_delete denial of service — Open5GS 5.3 Medium 2026-05-10
CVE-2026-8224 Open5GS PCF context.c pcf_sess_set_ipv6prefix denial of service — Open5GS 5.3 Medium 2026-05-10
CVE-2026-8223 Open5GS sm-policies Endpoint pcf_sess_sbi_discover_and_send denial of service — Open5GS 5.3 Medium 2026-05-10
CVE-2026-8222 Open5GS sm-policies Endpoint nbsf-handler.c pcf_nbsf_management_handle_register denial of service — Open5GS 5.3 Medium 2026-05-10

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