An attempt to access data using a null pointer causes a runtime error. When a program dereferences a pointer that is expected to be valid but turns out to be null, a null pointer dereference occurs. Null-pointer dereference defects often occur due to ineffective error handling or race conditions, and typically cause abnormal program termination. Before a pointer is dereferenced in C/C++ code, it must be checked to confirm that it is not equal to null.

The NPD checkers look for instances in which a null or possibly null pointer is dereferenced.

The NPD.CONST.CALL checker flags situations in which a null-pointer constant value might be passed to a function that dereferences it without checking it for null.

Vulnerability and risk

Null-pointer dereferences usually result in the failure of the process. These issues typically occur due to ineffective exception handling.

Mitigation and prevention

To avoid this vulnerability:

Check for a null value in the results of all functions that return values
Make sure all external inputs are validated
Explicitly initialize variables
Make sure that unusual exceptions are handled correctly

Vulnerable code example

1  void reassign(int *argument, int *p) {
2    if (goodEnough(argument)) return;
3    *argument = *p;
4  }
5  
6  void npd_const_call(int *argument) {
7    reassign(argument, 0);
8  }

Depending on the conditional statement at line 2 of this example, the npd_const_call function may dereference a null-pointer value in the constant 'argument'. This type of vulnerability can produce unexpected and unintended results.

Related checkers

External guidance

Extension

This checker can be extended through the Klocwork knowledge base. See Tuning C/C++ analysis for more information.