CWE一覧に戻る
CWE-590

ヒープ上にないメモリの解放

Free of Memory not on the Heap
脆弱性 作成中
JA

この製品は、malloc()、calloc()、realloc()などの関連するヒープ割り当て関数を使用して割り当てられていないメモリへのポインタに対してfree()を呼び出す。

無効なポインタ上で free() が呼び出されると、プログラムのメモリ管理データ構造が破損する可能性がある。この破損によりプログラムがクラッシュしたり、状況によっては攻撃者が制御可能なメモリー位置でfree()を動作させ、重要なプログラム変数を変更したりコードを実行したりする可能性がある。

EN

The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().

When free() is called on an invalid pointer, the program's memory management data structures may become corrupted. This corruption can cause the program to crash or, in some circumstances, an attacker may be able to cause free() to operate on controllable memory locations to modify critical program variables or execute code.

Scope: Integrity, Confidentiality, Availability / Impact: Execute Unauthorized Code or Commands; Modify Memory
Only free pointers that you have called malloc on previously. This is the recommended solution. Keep track of which pointers point at the beginning of valid chunks and free them only once.
Before freeing a pointer, the programmer should make sure that the pointer was previously allocated on the heap and that the memory belongs to the programmer. Freeing an unallocated pointer will cause undefined behavior in the program.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

For example, glibc in Linux provides protection against free of invalid pointers.
Use a language that provides abstractions for memory allocation and deallocation.
Use a tool that dynamically detects memory management problems, such as valgrind.
MITRE公式ページ — CWE-590