Access of Uninitialized Pointer

Incomplete Base
Structure: Simple
Description

This vulnerability occurs when a program tries to use a pointer variable before it has been assigned a valid memory address.

Extended Description

Using an uninitialized pointer means your code is reading from or writing to a random, unpredictable location in memory. This often crashes the program (causing a denial of service), but it can also lead to strange behavior, data corruption, or the execution of unintended functions if the pointer is called. An attacker who can control or predict what value ends up in that uninitialized pointer gains significant power. By carefully manipulating memory layout, they might steer the pointer to a location of their choosing, potentially enabling code execution, privilege escalation, or other serious security breaches.

Common Consequences 3
Scope: Confidentiality

Impact: Read Memory

If the uninitialized pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.

Scope: Availability

Impact: DoS: Crash, Exit, or Restart

If the uninitialized pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Scope: IntegrityConfidentialityAvailability

Impact: Execute Unauthorized Code or Commands

If the uninitialized pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Detection Methods 1
Automated Static AnalysisHigh
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.)
Observed Examples 19
CVE-2024-32878LLM product has a free of an uninitialized pointer
CVE-2019-3836Chain: secure communications library does not initialize a local variable for a data structure (Missing Initialization of a Variable), leading to access of an uninitialized pointer (Access of Uninitialized Pointer).
CVE-2018-14641Chain: C union member is not initialized (Missing Initialization of a Variable), leading to access of invalid pointer (Access of Uninitialized Pointer)
CVE-2010-0211chain: unchecked return value (Unchecked Return Value) leads to free of invalid, uninitialized pointer (Access of Uninitialized Pointer).
CVE-2009-2768Pointer in structure is not initialized, leading to NULL pointer dereference (NULL Pointer Dereference) and system crash.
CVE-2009-1721Free of an uninitialized pointer.
CVE-2009-1415Improper handling of invalid signatures leads to free of invalid pointer.
CVE-2009-0846Invalid encoding triggers free of uninitialized pointer.
CVE-2009-0040Crafted PNG image leads to free of uninitialized pointer.
CVE-2008-2934Crafted GIF image leads to free of uninitialized pointer.
CVE-2007-4682Access of uninitialized pointer might lead to code execution.
CVE-2007-4639Step-based manipulation: invocation of debugging function before the primary initialization function leads to access of an uninitialized pointer and code execution.
CVE-2007-4000Unchecked return values can lead to a write to an uninitialized pointer.
CVE-2007-2442zero-length input leads to free of uninitialized pointer.
CVE-2007-1213Crafted font leads to uninitialized function pointer.
CVE-2006-6143Uninitialized function pointer in freed memory is invoked
CVE-2006-4175LDAP server mishandles malformed BER queries, leading to free of uninitialized memory
CVE-2006-0054Firewall can crash with certain ICMP packets that trigger access of an uninitialized pointer.
CVE-2003-1201LDAP server does not initialize members of structs, which leads to free of uninitialized pointer if an LDAP request fails.
References 1
The Art of Software Security Assessment
Mark Dowd, John McDonald, and Justin Schuh
Addison Wesley
2006
ID: REF-62
Applicable Platforms
Languages:
C : UndeterminedC++ : Undetermined
Functional Areas
  1. Memory Management
Affected Resources
  1. Memory
Notes
MaintenanceThere are close relationships between incorrect pointer dereferences and other weaknesses related to buffer operations. There may not be sufficient community agreement regarding these relationships. Further study is needed to determine when these relationships are chains, composites, perspective/layering, or other types of relationships. As of September 2010, most of the relationships are being captured as chains.
TerminologyMany weaknesses related to pointer dereferences fall under the general term of "memory corruption" or "memory safety." As of September 2010, there is no commonly-used terminology that covers the lower-level variants.