CWE · MITRE source
CWE-404Improper Resource Shutdown or Release
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.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 3 mapping(s) from 2 framework(s): ATT&CK 2 (partial) · CAPEC 1 (partial)
NIST 800-53 r5 controls that address this weakness (4)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-10 | Network Disconnect | SC | Mandates explicit shutdown of the network connection at session conclusion, directly addressing improper resource release. |
SC-4 | Information in Shared System Resources | SC | Requires proper shutdown/release procedures that include overwriting or isolating data to block unintended transfer via reused system objects. |
CP-5 | Contingency Plan Update | CP | Contingency plan updates incorporate proper resource shutdown and release steps, preventing attackers from leveraging incomplete cleanup during recovery scenarios. |
SI-17 | Fail-safe Procedures | SI | Procedures can mandate orderly shutdown or release of resources when failures occur, preventing improper resource handling after a fault. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2017-6627 KEV | 10.0 | 7.5 | 0.0604 | 2017-09-07 |
CVE-2018-8120 KEV | 10.0 | 7.0 | 0.7372 | 2018-05-09 |
CVE-2018-8405 KEV | 10.0 | 7.8 | 0.0344 | 2018-08-15 |
CVE-2018-8406 KEV | 10.0 | 7.8 | 0.0344 | 2018-08-15 |
CVE-2018-8611 KEV | 10.0 | 7.8 | 0.0416 | 2018-12-12 |
CVE-2018-8639 KEV | 10.0 | 7.8 | 0.2235 | 2018-12-12 |
CVE-2022-44267 | 8.0 | 6.5 | 0.7658 | 2023-02-06 |
CVE-2023-24444 | 7.0 | 9.8 | 0.0115 | 2023-01-26 |
CVE-2024-31611 | 7.0 | 9.1 | 0.0057 | 2024-06-10 |
CVE-2018-8210 | 6.0 | 7.8 | 0.2471 | 2018-06-14 |
CVE-2018-8450 | 6.0 | 8.8 | 0.1608 | 2018-11-14 |
CVE-2023-3206 | 6.0 | 5.3 | 0.1871 | 2023-06-12 |
CVE-2025-1103 | 6.0 | 6.5 | 0.1127 | 2025-02-07 |
CVE-2010-4038 | 5.5 | 7.5 | 0.0167 | 2010-10-21 |
CVE-2016-8212 | 5.5 | 7.5 | 0.0192 | 2017-02-03 |
CVE-2017-1145 | 5.5 | 8.6 | 0.0191 | 2017-03-20 |
CVE-2017-5650 | 5.5 | 7.5 | 0.0828 | 2017-04-17 |
CVE-2016-10363 | 5.5 | 7.5 | 0.0132 | 2017-06-16 |
CVE-2012-2805 | 5.5 | 7.5 | 0.0192 | 2017-08-28 |
CVE-2017-0769 | 5.5 | 7.8 | 0.0041 | 2017-09-08 |
CVE-2017-11016 | 5.5 | 7.8 | 0.0014 | 2017-12-05 |
CVE-2017-11480 | 5.5 | 7.5 | 0.0144 | 2017-12-08 |
CVE-2017-1000411 | 5.5 | 7.5 | 0.0160 | 2018-01-31 |
CVE-2018-6592 | 5.5 | 7.8 | 0.0030 | 2018-02-19 |
CVE-2018-8124 | 5.5 | 7.0 | 0.0115 | 2018-05-09 |