Failure to Provide Specified Functionality |
Weakness ID: 684 (Weakness Base) | Status: Draft |
Description Summary
The code does not function according to its published specifications, potentially leading to incorrect usage.
Extended Description
When providing functionality to an external party, it is important that the software behaves in accordance with the details specified. Failing to document requirements or nuances can result in unintended behaviors for the caller, possibly leading to an exploitable state.
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 227 | Failure to Fulfill API Contract ('API Abuse') | Development Concepts (primary)699 Research Concepts (primary)1000 |
ChildOf | ![]() | 735 | CERT C Secure Coding Section 01 - Preprocessor (PRE) | Weaknesses Addressed by the CERT C Secure Coding Standard (primary)734 |
ParentOf | ![]() | 392 | Failure to Report Error in Status Code | Research Concepts (primary)1000 |
ParentOf | ![]() | 393 | Return of Wrong Status Code | Research Concepts (primary)1000 |
ParentOf | ![]() | 440 | Expected Behavior Violation | Research Concepts (primary)1000 |
ParentOf | ![]() | 446 | UI Discrepancy for Security Feature | Research Concepts (primary)1000 |
Mapped Taxonomy Name | Node ID | Fit | Mapped Node Name |
---|---|---|---|
CERT C Secure Coding | PRE09-C | Do not replace secure functions with less secure functions |
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 Description, Relationships | ||||
2008-11-24 | CWE Content Team | MITRE | Internal | |
updated Relationships, Taxonomy Mappings |