Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CWE CATEGORY:Authentication Errors
Category ID:1211
Vulnerability Mapping:Prohibited
Status:Draft
DetailsContent HistoryObserved CVE ExamplesReports
▼Summary

Weaknesses in this category are related to authentication components of a system. Frequently these deal with the ability to verify that an entity is indeed who it claims to be. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authentication capability.

▼Membership
NatureMappingTypeIDName
MemberOfProhibitedV699Software Development
HasMemberAllowedB289Authentication Bypass by Alternate Name
HasMemberAllowedB290Authentication Bypass by Spoofing
HasMemberAllowedB294Authentication Bypass by Capture-replay
HasMemberAllowedB295Improper Certificate Validation
HasMemberAllowedB301Reflection Attack in an Authentication Protocol
HasMemberAllowedB303Incorrect Implementation of Authentication Algorithm
HasMemberAllowedB305Authentication Bypass by Primary Weakness
HasMemberAllowedB306Missing Authentication for Critical Function
HasMemberAllowedB307Improper Restriction of Excessive Authentication Attempts
HasMemberAllowedB308Use of Single-factor Authentication
HasMemberAllowedB309Use of Password System for Primary Authentication
HasMemberAllowedB322Key Exchange without Entity Authentication
HasMemberAllowedB603Use of Client-Side Authentication
HasMemberAllowedB645Overly Restrictive Account Lockout Mechanism
HasMemberAllowedB804Guessable CAPTCHA
HasMemberAllowedB836Use of Password Hash Instead of Password for Authentication
Nature: MemberOf
Mapping: Prohibited
Type: View
ID: 699
Name: Software Development
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 289
Name: Authentication Bypass by Alternate Name
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 290
Name: Authentication Bypass by Spoofing
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 294
Name: Authentication Bypass by Capture-replay
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 295
Name: Improper Certificate Validation
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 301
Name: Reflection Attack in an Authentication Protocol
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 303
Name: Incorrect Implementation of Authentication Algorithm
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 305
Name: Authentication Bypass by Primary Weakness
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 306
Name: Missing Authentication for Critical Function
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 307
Name: Improper Restriction of Excessive Authentication Attempts
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 308
Name: Use of Single-factor Authentication
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 309
Name: Use of Password System for Primary Authentication
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 322
Name: Key Exchange without Entity Authentication
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 603
Name: Use of Client-Side Authentication
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 645
Name: Overly Restrictive Account Lockout Mechanism
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 804
Name: Guessable CAPTCHA
Nature: HasMember
Mapping: Allowed
Type: Base
ID: 836
Name: Use of Password Hash Instead of Password for Authentication
▼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