CWE-401: Missing Release of Memory after Effective Lifetime Skip to content

Security weakness

CWE-401 Missing Release of Memory after Effective Lifetime

A variant-level weakness that can lead to downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-401?

Missing Release of Memory after Effective Lifetime: The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Business impact

What CWE-401 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Crash, Exit, or Restart
  • DoS: Instability
  • DoS: Resource Consumption (CPU)

Free security check

Is CWE-401 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-401

Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Also known as: Memory Leak

Weakness ID
CWE-401
Type
Variant
Status
Draft
Likelihood of exploit
Medium
Applies to
C, C++
Introduced during
Implementation

Prevention

How to fix CWE-401, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Use an abstraction library to abstract away risky APIs. Not a complete solution.
    • Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
  2. 02

    Implementation

    • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391]. To help correctly and consistently manage memory when programming in C++, consider.

Detection and evidence

How CWE-401 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • FuzzingFuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs – either randomly or algorithmically – and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption.
  • Automated Dynamic AnalysisUse tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518] or valgrind [REF-480].
  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-2005-3119Memory leak because function does not free() an element of a data structure.
  • CVE-2004-0427Memory leak when counter variable is not decremented.
  • CVE-2002-0574Chain: reference count is not decremented, leading to memory leak in OS by sending ICMP packets.
  • CVE-2005-3181Kernel uses wrong function to release a data structure, preventing data from being properly tracked by other code.
  • CVE-2004-0222Memory leak via unknown manipulations as part of a protocol test suite.
  • CVE-2001-0136Memory leak via a series of the same command.

How we fix it

From finding to fixed: how Codefreex closes CWE-401

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-401: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-401?

CWE-401, “Missing Release of Memory after Effective Lifetime”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How serious is CWE-401?

MITRE rates the likelihood of exploit as Medium. It can affect availability, other, with impacts such as dos: crash, exit, or restart, dos: instability, dos: resource consumption (cpu). The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-401?

Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic. Use an abstraction library to abstract away risky APIs. Not a complete solution.

Can Codefreex check my site for CWE-401?

Yes. A senior engineer reviews your site, store or app for CWE-401 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-401 affect?

MITRE lists it as applicable to C, C++. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-401 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.