Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE CATEGORY:SFP Secondary Cluster: Incorrect Input Handling
Category ID:993
Vulnerability Mapping:Prohibited
Status:Incomplete
DetailsContent HistoryObserved CVE ExamplesReports
▼Summary

This category identifies Software Fault Patterns (SFPs) within the Incorrect Input Handling cluster.

▼Membership
NatureMappingTypeIDName
MemberOfProhibitedV888Software Fault Pattern (SFP) Clusters
HasMemberAllowedB241Improper Handling of Unexpected Data Type
HasMemberAllowedV198Use of Incorrect Byte Ordering
HasMemberAllowedB240Improper Handling of Inconsistent Structural Elements
HasMemberAllowed-with-ReviewC228Improper Handling of Syntactically Invalid Structure
HasMemberAllowedB229Improper Handling of Values
HasMemberAllowedV230Improper Handling of Missing Values
HasMemberAllowedV231Improper Handling of Extra Values
HasMemberAllowedV232Improper Handling of Undefined Values
HasMemberAllowedB233Improper Handling of Parameters
HasMemberDiscouragedV234Failure to Handle Missing Parameter
HasMemberAllowedV235Improper Handling of Extra Parameters
HasMemberAllowedV236Improper Handling of Undefined Parameters
HasMemberAllowedB237Improper Handling of Structural Elements
HasMemberAllowedV238Improper Handling of Incomplete Structural Elements
HasMemberAllowedV239Failure to Handle Incomplete Element
HasMemberAllowedB351Insufficient Type Distinction
HasMemberAllowedB354Improper Validation of Integrity Check Value
Nature: MemberOf
Mapping: Prohibited
Type: View
ID: 888
Name: Software Fault Pattern (SFP) Clusters
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 241
Name: Improper Handling of Unexpected Data Type
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 198
Name: Use of Incorrect Byte Ordering
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 240
Name: Improper Handling of Inconsistent Structural Elements
Nature: HasMember
Mapping: Allowed-with-Review
Type: Class
ID: 228
Name: Improper Handling of Syntactically Invalid Structure
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 229
Name: Improper Handling of Values
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 230
Name: Improper Handling of Missing Values
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 231
Name: Improper Handling of Extra Values
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 232
Name: Improper Handling of Undefined Values
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 233
Name: Improper Handling of Parameters
Nature: HasMember
Mapping: Discouraged
Type: Variant
ID: 234
Name: Failure to Handle Missing Parameter
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 235
Name: Improper Handling of Extra Parameters
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 236
Name: Improper Handling of Undefined Parameters
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 237
Name: Improper Handling of Structural Elements
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 238
Name: Improper Handling of Incomplete Structural Elements
Nature: HasMember
Mapping: Allowed
Type: Variant
ID: 239
Name: Failure to Handle Incomplete Element
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 351
Name: Insufficient Type Distinction
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 354
Name: Improper Validation of Integrity Check Value
▼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
▼Taxonomy Mappings
Taxonomy NameEntry IDFitEntry Name
▼References
Details not found