CWE-587: Assignment of a Fixed Address to a Pointer

Code Examples & CVEs

Demonstrative Examples

This code assumes a particular function will always be found at a particular address. It assigns a pointer to that address and calls the function.

The same function may not always be found at the same memory address. This could lead to a crash, or an attacker may alter the memory at the expected address, leading to arbitrary code execution.

BadC

int (*pt2Function) (float, char, char)=0x08040000;int result2 = (*pt2Function) (12, 'a', 'b');                      // Here we can inject code to execute.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-587 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-587, Assignment of a Fixed Address to a Pointer, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Assignment of a Fixed Address to a Pointer during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis, and Automated Dynamic Analysis; recorded impacts include Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart, Reduce Maintainability, Reduce Reliability, and Read Memory. Use these source-defined anchors to turn CWE-587 into implementation, review, and verification checks for the affected component.

CWE-587: Assignment of a Fixed Address to a Pointer — MITRE CWE

Triage CWE-587 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-587, Assignment of a Fixed Address to a Pointer, 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 Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-587

Apply MITRE's full root-cause mapping guidance when using CWE-587, Assignment of a Fixed Address to a Pointer. 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 Guidance — MITRE CWE

Validate CWE-587 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-587, Assignment of a Fixed Address to a Pointer. 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 Tips — MITRE CWE

Frequently Asked Questions

What is CWE-587: Assignment of a Fixed Address to a Pointer?+

CWE-587: Assignment of a Fixed Address to a Pointer is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product sets a pointer to a specific address other than NULL or 0. Using a fixed address is not portable, because that address will probably not be valid in all environments or platforms.

What are the security consequences of Assignment of a Fixed Address to a Pointer?+

If exploited, CWE-587 (Assignment of a Fixed Address to a Pointer) it can compromise Integrity, Confidentiality and Availability, leading to outcomes such as Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart, Reduce Maintainability, Reduce Reliability, Read Memory and Modify Memory.

How do you prevent or mitigate Assignment of a Fixed Address to a Pointer?+

Recommended mitigations for CWE-587 include: Never set a pointer to a fixed address.

Which programming languages are affected by Assignment of a Fixed Address to a Pointer?+

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

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

A CWE (Common Weakness Enumeration) like CWE-587 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.

CWE-587: Assignment of a Fixed Address to a Pointer

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-587 with SSDF evidence

Address Assignment of a Fixed Address to a Pointer during Implementation

Triage CWE-587 against known exploitation evidence

Apply precise root-cause mapping to CWE-587

Validate CWE-587 with root-cause mapping checks

Frequently Asked Questions

Learn More