CWE一覧に戻る
CWE-401

有効期限後のメモリ解放の行方

Missing Release of Memory after Effective Lifetime
脆弱性 レビュー中
JA

この製品は、割り当てられたメモリが使用された後の追跡と解放が十分でないため、メモリを再割り当てして再利用することができない。

EN

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

Scope: Availability / Impact: DoS: Crash, Exit, or Restart; DoS: Instability; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
Scope: Other / Impact: Reduce Performance
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 using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
Use an abstraction library to abstract away risky APIs. Not a complete solution.
The Boehm-Demers-Weiser Garbage Collector or valgrind can be used to detect leaks in code.
MITRE公式ページ — CWE-401