Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-476 (空指针解引用) — Vulnerability Class 1557

1557 vulnerabilities classified as CWE-476 (空指针解引用). AI Chinese analysis included.

CWE-476 represents a critical memory management weakness where software attempts to access memory through a pointer that holds a NULL value instead of a valid address. This error typically occurs when a function fails to allocate memory or validate input, yet the code proceeds to dereference the resulting null reference without checking its status. Attackers exploit this vulnerability by triggering the null condition, often causing the application to crash and resulting in a denial of service. In more complex scenarios, if the NULL pointer is manipulated to point to executable code, it may lead to arbitrary code execution or privilege escalation. To prevent this, developers must rigorously validate all pointers before use, ensuring they are not NULL. Implementing defensive programming practices, such as using assertions during development and comprehensive error handling in production, helps mitigate the risk of dereferencing invalid memory addresses.

MITRE CWE Description
The product dereferences a pointer that it expects to be valid but is NULL.
Common Consequences (2)
Availability DoS: Crash, Exit, or Restart
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.
Integrity, Confidentiality Execute Unauthorized Code or Commands, Read Memory, Modify Memory
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.
Mitigations (5)
Implementation For 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].
Requirements Select a programming language that is not susceptible to these issues.
Implementation Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
Effectiveness: Moderate
Architecture and Design Identify 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.
Implementation Explicitly initialize all variables and other data stores, either during declaration or just before the first usage.
Examples (2)
This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.
void host_lookup(char *user_supplied_addr){ struct hostent *hp; in_addr_t *addr; char hostname[64]; in_addr_t inet_addr(const char *cp); /*routine that ensures user_supplied_addr is in the right format for conversion */ validate_addr_form(user_supplied_addr); addr = inet_addr(user_supplied_addr); hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET); strcpy(hostname, hp->h_name); }
Bad · C
In the following code, the programmer assumes that the system always has a property named "cmd" defined. If an attacker can control the program's environment so that "cmd" is not defined, the program throws a NULL pointer exception when it attempts to call the trim() method.
String cmd = System.getProperty("cmd"); cmd = cmd.trim();
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2022-41999 OpenImageIO 代码问题漏洞 — OpenImageIO 7.5 - 2022-12-23
CVE-2022-43593 OpenImageIO 代码问题漏洞 — OpenImageIO 5.9 - 2022-12-23
CVE-2022-43594 OpenImageIO 代码问题漏洞 — OpenImageIO 5.9 Medium 2022-12-23
CVE-2022-43595 OpenImageIO 代码问题漏洞 — OpenImageIO 5.9 Medium 2022-12-23
CVE-2022-43603 OpenImageIO 代码问题漏洞 — OpenImageIO 7.5 - 2022-12-23
CVE-2022-41972 Contiki-NG contains NULL Pointer Dereference in BLE L2CAP module — contiki-ng 2.9 Low 2022-12-16
CVE-2022-3109 FFmpeg 代码问题漏洞 — FFmpeg 7.5 - 2022-12-16
CVE-2022-23526 Helm contains Denial of service through schema file — helm 5.3 Medium 2022-12-15
CVE-2022-23525 Helm vulnerable to Denial of service via NULL Pointer Dereference — helm 5.3 Medium 2022-12-15
CVE-2022-3104 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3105 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3106 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3107 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3110 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3111 Linux kernel 代码问题漏洞 — Kernel 7.8 - 2022-12-14
CVE-2022-3112 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3113 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3114 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-3115 Linux kernel 代码问题漏洞 — Kernel 5.5 - 2022-12-14
CVE-2022-41278 Siemens部分产品 代码问题漏洞 — JT2Go 3.3 Low 2022-12-13
CVE-2022-41279 Siemens部分产品 代码问题漏洞 — JT2Go 3.3 Low 2022-12-13
CVE-2022-41280 Siemens部分产品 代码问题漏洞 — JT2Go 3.3 Low 2022-12-13
CVE-2022-43590 Callback Technologies CBFS Filter 代码问题漏洞 — CBFS Filter 5.5 - 2022-11-28
CVE-2022-43589 Callback Technologies CBFS Filter 代码问题漏洞 — CBFS Filter 5.5 - 2022-11-28
CVE-2022-43588 Callback Technologies CBFS Filter 代码问题漏洞 — CBFS Filter 5.5 - 2022-11-28
CVE-2022-4127 Linux kernel 代码问题漏洞 — Linux kernel (io_uring) 5.5 - 2022-11-28
CVE-2022-4128 Linux kernel 代码问题漏洞 — Linux kernel (mptcp) 5.5 - 2022-11-28
CVE-2022-31613 NVIDIA GPU Display Driver 代码问题漏洞 — NVIDIA Cloud Gaming (guest driver) 7.1 High 2022-11-18
CVE-2022-31615 NVIDIA graphics driver 代码问题漏洞 — GeForce, Workstation, Compute 5.5 Medium 2022-11-18
CVE-2022-34665 NVIDIA GPU Display Driver 代码问题漏洞 — NVIDIA Cloud Gaming (guest driver), NVIDIA Cloud Gaming (Virtual GPU Manager) 6.5 Medium 2022-11-18

Vulnerabilities classified as CWE-476 (空指针解引用) represent 1557 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.