CWE-822: Untrusted Pointer Dereference

BaseIncomplete

The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.

View on MITRE
Back to CWE Lookup

Extended Description

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.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
CC++Memory-Unsafe
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect Untrusted Pointer Dereference with Automated Static Analysis

Documented detection approaches include Automated Static Analysis, and Automated Dynamic Analysis; recorded impacts include Read Memory, DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, and Modify Memory; the entry maps to CAPEC-129. Use these source-defined anchors to turn CWE-822 into implementation, review, and verification checks for the affected component.

CWE-822: Untrusted Pointer DereferenceMITRE CWE

Prevent CWE-822 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-822, Untrusted Pointer Dereference, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Triage CWE-822 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-822, Untrusted Pointer Dereference, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-822

Apply MITRE's full root-cause mapping guidance when using CWE-822, Untrusted Pointer Dereference. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-822 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-822, Untrusted Pointer Dereference. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-822: Untrusted Pointer Dereference?+

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.

What are the security consequences of Untrusted Pointer Dereference?+

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.

Which programming languages are affected by Untrusted Pointer Dereference?+

CWE-822 commonly affects C, C++ and Memory-Unsafe. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Untrusted Pointer Dereference?+

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.

What is the difference between a CWE and a CVE?+

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.

Learn More

Advertisement