Untrusted Pointer Dereference

Incomplete Base
Structure: Simple
Description

This vulnerability occurs when software takes a value from an untrusted source, treats it as a memory address (a pointer), and then accesses that memory location directly for reading or writing.

Extended Description

An attacker can exploit this by providing a pointer to unexpected memory regions. If the software writes to this location, it could corrupt critical data, crash the program, or even allow code execution. If it reads from the location, it might leak sensitive information, cause a crash, or use an arbitrary value from memory, leading to unpredictable behavior. This weakness appears in several forms. For example, the untrusted value might be called directly as a function pointer. In operating system kernels, untrusted pointers can cross the boundary from user space into privileged memory via system calls. It also often arises when code designed for a trusted, isolated environment is later exposed to untrusted network input without proper validation of pointer values.

Common Consequences 3
Scope: Confidentiality

Impact: Read Memory

If the untrusted 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 untrusted pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly.

Scope: IntegrityConfidentialityAvailability

Impact: Execute Unauthorized Code or CommandsModify Memory

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

Observed Examples 8
CVE-2007-5655message-passing framework interprets values in packets as pointers, causing a crash.
CVE-2010-2299labeled as a "type confusion" issue, also referred to as a "stale pointer." However, the bug ID says "contents are simply interpreted as a pointer... renderer ordinarily doesn't supply this pointer directly". The "handle" in the untrusted area is replaced in one function, but not another - thus also, effectively, exposure to wrong sphere (Exposure of Resource to Wrong Sphere).
CVE-2009-1719Untrusted dereference using undocumented constructor.
CVE-2009-1250An error code is incorrectly checked and interpreted as a pointer, leading to a crash.
CVE-2009-0311An untrusted value is obtained from a packet and directly called as a function pointer, leading to code execution.
CVE-2010-1818Undocumented attribute in multimedia software allows "unmarshaling" of an untrusted pointer.
CVE-2010-3189ActiveX control for security software accepts a parameter that is assumed to be an initialized pointer.
CVE-2010-1253Spreadsheet software treats certain record values that lead to "user-controlled pointer" (might be untrusted offset, not untrusted pointer).
Related Attack Patterns
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.