CWE-690 상세 정보

The product does not check for an error after calling a function that can return with a NULL pointer if the function fails, which leads to a resultant NULL pointer dereference.

배경 세부 정보

취약점 도입 방식

Implementation : A typical occurrence of this weakness occurs when an application includes user-controlled input to a malloc() call. The related code might be correct with respect to preventing buffer overflows, but if a large value is provided, the malloc() will fail due to insufficient memory. This problem also frequently occurs when a parsing routine expects that certain elements will always be present. If malformed input is provided, the parser might return NULL. For example, strtok() can return NULL.

적용 가능한 플랫폼

언어

클래스: Memory-Unsafe (Often)
이름: C (Undetermined)
이름: C++ (Undetermined)

일반적인 결과

관찰된 예시

탐지 방법

Black Box

This typically occurs in rarely-triggered error conditions, reducing the chances of detection during black box testing.

White Box

Code analysis can require knowledge of API behaviors for library functions that might return NULL, reducing the chances of detection when unknown libraries are used.

Automated Dynamic Analysis

Use 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].
효과성 : Moderate

취약점 매핑 메모

근거 : This CWE entry is a named chain, which combines multiple weaknesses.
댓글 : Mapping to each separate weakness in the chain would be more precise.

참고 자료

REF-1518

AddressSanitizer
https://clang.llvm.org/docs/AddressSanitizer.html

제출

수정 사항