Détail du 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.

While unchecked return value weaknesses are not limited to returns of NULL pointers (see the examples in CWE-252), functions often return NULL to indicate an error status. When this error condition is not checked, a NULL pointer dereference can occur.

Modes d'introduction

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.

Plateformes applicables

Langue

Class: Memory-Unsafe (Often)
Name: C (Undetermined)
Name: C++ (Undetermined)

Conséquences courantes

Exemples observés

Méthodes de détection

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].
Efficacité : Moderate

Notes de cartographie des vulnérabilités

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

Références

REF-1518

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

Soumission

Modifications