Official definition

ByMitre CWE

The product dereferences a pointer that it expects to be valid but is NULL.

Characteristics

Alternate terms

NPD — Common abbreviation for Null Pointer Dereference
null deref — Common abbreviation for Null Pointer Dereference
NPE — Common abbreviation for Null Pointer Exception
nil pointer dereference — used for access of nil in Go programs

Modes of introduction

Implementation

Common consequences

Impact	Scope	Explanation
DoS: Crash, Exit, or Restart	Availability	NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.
Execute Unauthorized Code or Commands, Read Memory, Modify Memory	Integrity, Confidentiality	In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.

Risk mitigations

ImplementationFor any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished [REF-1484].
RequirementsSelect a programming language that is not susceptible to these issues.
Implementation · Effectiveness: ModerateCheck the results of all functions that return a value and verify that the value is non-null before acting upon it.Checking the return value of the function will typically be sufficient, however beware of race conditions (CWE-362) in a concurrent environment. This solution does not handle the use of improperly initialized variables (CWE-665).
Architecture and DesignIdentify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
ImplementationExplicitly initialize all variables and other data stores, either during declaration or just before the first usage.

Detection methods

Method	Approach	Effectiveness
Automated Dynamic Analysis	This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.	Moderate
Manual Dynamic Analysis	Identify error conditions that are not likely to occur during normal usage and trigger them. For example, run the program under low memory conditions, run with insufficient privileges or permissions, interrupt a transaction before it is completed, or disable connectivity to basic network services such as DNS. Monitor the software for any unexpected behavior. If you trigger an unhandled exception or similar error that was discovered and handled by the application's environment, it may still indicate unexpected conditions that were not handled by the application itself.	—
Automated Static Analysis	Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)	High
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].Crafted inputs are necessary to reach the code containing the error, such as generated by fuzzers. Also, these tools may reduce performance, and they only report the error condition - not the original mistake that led to the error.	Moderate

Representative vulnerabilities

Below are representative vulnerabilities related to this CWE, prioritized by severity.

Sources (9)

MITRE CWE

CWE Terms of Use The CLASP Application Security Process

CWE-476: NULL Pointer Dereference

What is CWE-476?

Data statistics

Vulnerabilities mapped to CWE-476

Vulnerabilities in CISA KEV for CWE-476

Official definition

Characteristics

Alternate terms

Modes of introduction

Common consequences

Risk mitigations

Detection methods

Representative vulnerabilities

Run an in-depth assessment with complete web risk management