Reliance on Undefined, Unspecified, or Implementation-Defined Behavior

Opis

The product 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.

This can lead to resultant weaknesses when the required properties change, such as when the product is ported to a different platform or if an interaction error (CWE-435) occurs.

Skutki

• Other

  Reduce Maintainability; Unexpected State; Quality Degradation

Przykłady podatności

• 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.

Słabość nadrzędna

• CWE-710 Improper Adherence to Coding Standards

Słabości podrzędne

• CWE-474 Use of Function with Inconsistent Implementations
• CWE-562 Return of Stack Variable Address
• CWE-587 Assignment of a Fixed Address to a Pointer
• CWE-588 Attempt to Access Child of a Non-structure Pointer
• CWE-1038 Insecure Automated Optimizations
• CWE-1102 Reliance on Machine-Dependent Data Representation
• CWE-1103 Use of Platform-Dependent Third Party Components
• CWE-1105 Insufficient Encapsulation of Machine-Dependent Functionality

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific