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-8123 Open5GS NSSF message.c ogs_sbi_discovery_option_add_snssais denial of service — Open5GS 4.3 Medium 2026-05-08
CVE-2026-8122 Open5GS NSSF message.c ogs_sbi_discovery_option_add_service_names denial of service — Open5GS 4.3 Medium 2026-05-08
CVE-2026-8121 Open5GS NSSF conv.c ogs_sbi_parse_plmn_list denial of service — Open5GS 4.3 Medium 2026-05-08
CVE-2026-8120 Open5GS NSSF nnssf-handler.c denial of service — Open5GS 4.3 Medium 2026-05-08
CVE-2026-8119 Open5GS NSSF nghttp2-server.c ogs_sbi_stream_find_by_id denial of service — Open5GS 3.3 Low 2026-05-08
CVE-2026-7781 Open5GS amf-3gpp-access Endpoint nudm-handler.c udm_nudm_uecm_handle_amf_registration_update denial of service — Open5GS 4.3 Medium 2026-05-04
CVE-2026-7780 Open5GS smf-registrations Endpoint udm-sm.c udm_state_operational denial of service — Open5GS 4.3 Medium 2026-05-04
CVE-2026-7779 Open5GS authentication-subscription Endpoint nudr-handler.c udm_nudr_dr_handle_subscription_authentication denial of service — Open5GS 4.3 Medium 2026-05-04
CVE-2026-7740 justdan96 tsMuxer vvc.cpp setFPS denial of service — tsMuxer 3.3 Low 2026-05-04
CVE-2026-7739 justdan96 tsMuxer hevc.cpp setFPS denial of service — tsMuxer 3.3 Low 2026-05-04
CVE-2026-7734 osrg GoBGP SRv6 L3 Service prefix_sid.go SRv6L3ServiceAttribute.DecodeFromBytes denial of service — GoBGP 5.3 Medium 2026-05-04
CVE-2026-7708 Open5GS UDR subscription.c ogs_dbi_subscription_data denial of service — Open5GS 4.3 Medium 2026-05-03
CVE-2026-7707 Open5GS UDR nudr-handler.c udr_nudr_dr_handle_subscription_context denial of service — Open5GS 4.3 Medium 2026-05-03
CVE-2026-7706 Open5GS AMF gmm-handler.c gmm_handle_service_request denial of service — Open5GS 4.3 Medium 2026-05-03
CVE-2026-7601 Open5GS AMF gmm-handler.c denial of service — Open5GS 4.3 Medium 2026-05-02
CVE-2026-7587 Open5GS AMF nsmf-handler.c amf_nsmf_pdusession_handle_update_sm_context denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2026-7586 Open5GS AMF nudm-handler.c ogs_id_get_value denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2026-7585 Open5GS AMF nudm-handler.c amf_nudm_sdm_handle_provisioned denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2026-7583 Open5GS BSF context.c bsf_sess_find_by_ipv6prefix denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2026-7536 Open5GS BSF pcfBindings bsf_sess_add_by_ip_address denial of service — Open5GS 5.3 Medium 2026-05-01
CVE-2026-7535 Open5GS transfer-update denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2026-7518 Open5GS AMF SBI Endpoint sdmsubscription-notify amf_namf_callback_handle_sdm_data_change_notify denial of service — Open5GS 4.3 Medium 2026-05-01
CVE-2025-43935 Dell PowerScale OneFS 安全漏洞 — PowerScale OneFS 4.4 Medium 2026-04-16
CVE-2026-35667 OpenClaw < 2026.3.24 - Improper Process Termination via Unpatched killProcessTree in shell-utils.ts — OpenClaw 6.1 Medium 2026-04-10
CVE-2026-5661 Free5GC NGSetupRequest denial of service — Free5GC 5.3 Medium 2026-04-06
CVE-2026-5313 Nothings stb GIF Decoder stb_image.h stbi__gif_load_next denial of service — stb 4.3 Medium 2026-04-01
CVE-2026-4988 Open5GS CCA Message smf_s6b denial of service — Open5GS 3.7 Low 2026-03-27
CVE-2026-4531 Free5GC AMF handler.go HandleRegistrationComplete denial of service — Free5GC 5.3 Medium 2026-03-22
CVE-2026-4240 Open5GS CCA smf_s6b_sta_cb denial of service — Open5GS 5.3 Medium 2026-03-16
CVE-2025-13901 Schneider Electric多款产品 安全漏洞 — Modicon M241/M251 5.3AI Medium AI 2026-03-10

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