Use of Function with Inconsistent Implementations

Opis

The code uses a function that has inconsistent implementations across operating systems and versions.

The use of inconsistent implementations can cause changes in behavior when the code is ported or built under a different environment than the programmer expects, which can lead to security problems in some cases.

The implementation of many functions varies by platform, and at times, even by different versions of the same platform. Implementation differences can include:

- Slight differences in the way parameters are interpreted leading to inconsistent results.

- Some implementations of the function carry significant security risks.

- The function might not be defined on all platforms.

- The function might change which return codes it can provide, or change the meaning of its return codes.

Skutki

• Other

  Quality Degradation; Varies by Context

Zapobieganie

• Architecture and Design, Requirements

  Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.

Słabość nadrzędna

• CWE-758 Reliance on Undefined, Unspecified, or Implementation-Defined Behavior

Słabości podrzędne

• CWE-589 Call to Non-ubiquitous API

Kiedy powstaje

• Implementation

Dotyczy

C, PHP, Not Language-Specific

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005