CWE-474 — Use of Function with Inconsistent Implementations
CWE-474: Use of Function with Inconsistent Implementations
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Draft |
| Likelihood of exploit | — |
Description
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.
Common consequences
- Other: Quality Degradation, Varies by Context
Mitigations
Architecture and Design — Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.
References
- CWE page: https://cwe.mitre.org/data/definitions/474.html
- CWE list: https://cwe.mitre.org/data/index.html