Use of Function with Inconsistent Implementations |
Weakness ID: 474 (Weakness Base) | Status: Draft |
Description Summary
The code uses a function that has inconsistent implementations across operating systems and versions, which might cause security-relevant portability problems.
Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level. |
The behavior of functions in this category varies by operating system, and at times, even by operating system version. 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. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 398 | Indicator of Poor Code Quality | Development Concepts (primary)699 Seven Pernicious Kingdoms (primary)700 Research Concepts (primary)1000 |
ParentOf | ![]() | 589 | Call to Non-ubiquitous API | Research Concepts (primary)1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
7 Pernicious Kingdoms | Inconsistent Implementations |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
7 Pernicious Kingdoms | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Potential Mitigations, Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Applicable Platforms, Relationships, Other Notes, Taxonomy Mappings | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2008-04-11 | Inconsistent Implementations | |||