Reliance on Undefined, Unspecified, or Implementation-Defined Behavior |
Weakness ID: 758 (Weakness Class) | Status: Incomplete |
Description Summary
The software uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity.
Extended Description
This can lead to resultant weaknesses when the required properties change, such as when the software is ported to a different platform or if an interaction error (CWE-435) occurs.
Reference | Description |
---|---|
CVE-2006-1902 | Change in C compiler behavior causes resultant buffer overflows in programs that depend on behaviors that were undefined in the C standard. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 710 | Coding Standards Violation | Research Concepts (primary)1000 |
ParentOf | ![]() | 188 | Reliance on Data/Memory Layout | Research Concepts (primary)1000 |
ParentOf | ![]() | 587 | Assignment of a Fixed Address to a Pointer | Research Concepts1000 |
ParentOf | ![]() | 588 | Attempt to Access Child of a Non-structure Pointer | Research Concepts1000 |
ParentOf | ![]() | 733 | Compiler Optimization Removal or Modification of Security-critical Code | Research Concepts1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
CERT C Secure Coding | MSC14-C | Do not introduce unnecessary platform dependencies | |
CERT C Secure Coding | MSC15-C | Do not depend on undefined behavior |