RNPD.DEREFSuspicious dereference of pointer before null checkAn 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 RNPD.DEREF checker finds instances in which a pointer is dereferenced before a null check. When there are no pointer changes on the trace between the dereference and the check, it is likely that the pointer is null at dereferencing, or the null check is improper. Vulnerability and riskNull-pointer dereferences usually result in the failure of the process. These issues typically occur due to ineffective exception handling. A dereference before the null check can result in:
Mitigation and preventionTo avoid this vulnerability:
Vulnerable code example1 void rnpd_1(int* t, int v) { 2 *t = 0; // t is dereferenced unconditionally 3 if (v < 0) v = -v; 4 if (t) *t = v; // t is verified before dereference 5 } In this example, the code dereferences 't' twice, once without any verification in line 2, and once guarded with a null check in line 4. Klocwork flags line 4, in which the null check occurs after the dereference. Of course, if the pointer is null, the application will crash after first dereference. Related checkers |