Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE CATEGORY:Error Conditions, Return Values, Status Codes
Category ID:389
Vulnerability Mapping:Prohibited
Status:Incomplete
DetailsContent HistoryObserved CVE ExamplesReports
▼Summary

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.

▼Membership
NatureMappingTypeIDName
MemberOfProhibitedV699Software Development
HasMemberAllowedB209Generation of Error Message Containing Sensitive Information
HasMemberAllowedB248Uncaught Exception
HasMemberAllowedB252Unchecked Return Value
HasMemberAllowedB253Incorrect Check of Function Return Value
HasMemberAllowedB390Detection of Error Condition Without Action
HasMemberProhibitedB391Unchecked Error Condition
HasMemberAllowedB392Missing Report of Error Condition
HasMemberAllowedB393Return of Wrong Status Code
HasMemberAllowedB394Unexpected Status Code or Return Value
HasMemberAllowedB395Use of NullPointerException Catch to Detect NULL Pointer Dereference
HasMemberAllowedB396Declaration of Catch for Generic Exception
HasMemberAllowedB397Declaration of Throws for Generic Exception
HasMemberAllowedB544Missing Standardized Error Handling Mechanism
HasMemberAllowedB584Return Inside Finally Block
HasMemberAllowedB617Reachable Assertion
HasMemberAllowedB756Missing Custom Error Page
Nature: MemberOf
Mapping: Prohibited
Type: View
ID: 699
Name: Software Development
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 209
Name: Generation of Error Message Containing Sensitive Information
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 248
Name: Uncaught Exception
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 252
Name: Unchecked Return Value
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 253
Name: Incorrect Check of Function Return Value
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 390
Name: Detection of Error Condition Without Action
Nature: HasMember
Mapping: Prohibited
Type: Base
ID: 391
Name: Unchecked Error Condition
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 392
Name: Missing Report of Error Condition
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 393
Name: Return of Wrong Status Code
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 394
Name: Unexpected Status Code or Return Value
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 395
Name: Use of NullPointerException Catch to Detect NULL Pointer Dereference
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 396
Name: Declaration of Catch for Generic Exception
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 397
Name: Declaration of Throws for Generic Exception
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 544
Name: Missing Standardized Error Handling Mechanism
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 584
Name: Return Inside Finally Block
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 617
Name: Reachable Assertion
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 756
Name: Missing Custom Error Page
▼Vulnerability Mapping Notes
Usage:Prohibited
Reason:
Rationale:

This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.

Comments:

See member weaknesses of this category.

▼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.

N/A

▼Taxonomy Mappings
Taxonomy NameEntry IDFitEntry Name
▼References
Reference ID: REF-44
Title: 24 Deadly Sins of Software Security
Version: v4.15
Author: Michael Howard, David LeBlanc, John Viega
Publication:
McGraw-Hill
Publisher:
Edition:
URL:
URL Date:
Day:N/A
Month:N/A
Year:2010
Details not found