CWE-389
Grouping ProhibitedError Conditions, Return Values, Status Codes
Status: Incomplete
This category includes weaknesses that occur if a function does not generate the correct return/status code, or if the application does not handle all possible return/status codes that could be generated by a function. This type of problem is most often found in conditions that are rarely encountered during the normal operation of the product. Presumably, most bugs related to common conditions are found and eliminated during development and testing. In some cases, the attacker can directly control or influence the environment to trigger the rare conditions.
Grouping entries organize the catalogue and should not be used to map the root cause of a vulnerability.
Mapping guidance
This entry is a Grouping. Using groupings for mapping has been discouraged since 2019. They are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.
See member weaknesses of this category.
Relationships and members
Notes
Other
Many researchers focus on the resultant weaknesses and do not necessarily diagnose whether a rare condition is the primary factor. However, since 2005 it seems to be reported more frequently than in the past. This subject needs more study.
Content history
updated Relationships, Other_Notes, Taxonomy_Mappings
updated Description
updated Other_Notes, Weakness_Ordinalities
updated Applicable_Platforms, Description, Other_Notes, References, Relationships, Research_Gaps, Taxonomy_Mappings, Weakness_Ordinalities
updated Relationships
updated Relationships
updated Mapping_Notes, Relationships
updated Mapping_Notes
updated Mapping_Notes, Type
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.