CWE-587 Detail

CWE-587

Name

Assignment of a Fixed Address to a Pointer

Status

Draft

Published

2006-12-15
00h00 +00:00

Modified

2024-02-29
00h00 +00:00

Official links

CWE Mitre.org

Notifications for a CWE

Stay informed of any changes for a specific CWE.

Notifications manage

List of Notifications

Notifications for a CWE

Stay informed of any changes for a specific CWE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specify the CWE ID you wish to monitor.

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

Name: Assignment of a Fixed Address to a Pointer

The product sets a pointer to a specific address other than NULL or 0.

CWE Description

Using a fixed address is not portable, because that address will probably not be valid in all environments or platforms.

General Informations

Modes Of Introduction

Implementation

Applicable Platforms

Language

Name: C (Undetermined)
Name: C++ (Undetermined)
Name: C# (Undetermined)
Class: Assembly (Undetermined)

Common Consequences

Scope	Impact	Likelihood
Integrity Confidentiality Availability	Execute Unauthorized Code or Commands Note: If one executes code at a known location, an attacker might be able to inject code there beforehand.
Availability	DoS: Crash, Exit, or Restart, Reduce Maintainability, Reduce Reliability Note: If the code is ported to another platform or environment, the pointer is likely to be invalid and cause a crash.
Confidentiality Integrity	Read Memory, Modify Memory Note: The data at a known pointer location can be easily read or influenced by an attacker.

Potential Mitigations

Phases : Implementation
Never set a pointer to a fixed address.

Vulnerability Mapping Notes

Justification : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comment : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Submission

Name	Organization	Date	Date release	Version
CWE Content Team	MITRE	2006-12-15 +00:00	2006-12-15 +00:00	Draft 5

Modifications

Name	Organization	Date	Comment
Eric Dalci	Cigital	2008-07-01 +00:00	updated Time_of_Introduction
	KDM Analytics	2008-08-01 +00:00	added/updated white box definitions
CWE Content Team	MITRE	2008-09-08 +00:00	updated Applicable_Platforms, Description, Relationships, Other_Notes, Weakness_Ordinalities
CWE Content Team	MITRE	2008-11-24 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2009-03-10 +00:00	updated Relationships
CWE Content Team	MITRE	2009-07-27 +00:00	updated Common_Consequences, Description, Other_Notes
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2011-09-13 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2012-05-11 +00:00	updated Demonstrative_Examples, Relationships
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Applicable_Platforms, Taxonomy_Mappings, White_Box_Definitions
CWE Content Team	MITRE	2019-01-03 +00:00	updated Relationships
CWE Content Team	MITRE	2021-03-15 +00:00	updated Common_Consequences, Weakness_Ordinalities
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated Relationships, Time_of_Introduction, Type
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-02-29 +00:00	updated Demonstrative_Examples