The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
View on MITREAn attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to: The untrusted value is directly invoked as a function call. In OS kernels or drivers where there is a boundary between "userland" and privileged memory spaces, an untrusted pointer might enter through an API or system call (see CWE-781 for one such example). Inadvertently accepting the value from an untrusted control sphere when it did not have to be accepted as input at all. This might occur when the code was originally developed to be run by a single user in a non-networked environment, and the code is then ported to or otherwise exposed to a networked environment.
If the untrusted pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.
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.
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.
No mitigation information available for this CWE.
No detection method information available for this CWE.
message-passing framework interprets values in packets as pointers, causing a crash.
View Detailslabeled 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 (CWE-668).
View DetailsAn error code is incorrectly checked and interpreted as a pointer, leading to a crash.
View DetailsAn untrusted value is obtained from a packet and directly called as a function pointer, leading to code execution.
View DetailsUndocumented attribute in multimedia software allows "unmarshaling" of an untrusted pointer.
View DetailsActiveX control for security software accepts a parameter that is assumed to be an initialized pointer.
View DetailsSpreadsheet software treats certain record values that lead to "user-controlled pointer" (might be untrusted offset, not untrusted pointer).
View DetailsNo relationship information available for this CWE.
CWE-822: Untrusted Pointer Dereference is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer. An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to: The untrusted value is directly invoked as a function call. In OS kernels or drivers where there is a boundary between "userland" and privileged memory spaces, an untrusted pointer might enter through an API or system call (see CWE-781 for one such example). Inadvertently accepting the value from an untrusted control sphere when it did not have to be accepted as input at all. This might occur when the code was originally developed to be run by a single user in a non-networked environment, and the code is then ported to or otherwise exposed to a networked environment.
If exploited, CWE-822 (Untrusted Pointer Dereference) it can compromise Confidentiality, Availability and Integrity, leading to outcomes such as Read Memory, DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands and Modify Memory.
MITRE documents real CVEs mapped to CWE-822, including CVE-2007-5655, CVE-2010-2299, CVE-2009-1719, CVE-2009-1250 and CVE-2009-0311. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-822 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.