This attack is often the result of one or more of the following:
User names (IDs, account names) may be guessable, published elsewhere, or are simply email addresses Authentication and related mechanisms may indicate whether a username is valid or not (registration, password reset/recovery, username recovery, change password, change email address) Missing authentication failure detection Missing monitoring to identify attacks against multiple user accounts, utilizing the same password Additionally another web or non-web application (e.g. mobile app, telephone service) that utilises the same credentials has one or more of the above problems.
NB: This card relates to user names. See AT 7 for the similar password cracking (brute forcing, dictionary attacks, guessing, credential stuffing, credential cracking).
Sebastien can easily identify user names or can enumerate them
Owasp ASVS (4.0): 2.2.1 ,4.1.5
Capec: 383
Owasp SCP: 33,53
Owasp Appsensor: AE1
Safecode: 28
ASVS V2.2 - General Authenticator Requirements
ASVS V4.1 - General Access Control Design
Password Guessing/Brute Force Attacks
Session Hijacking (Man-in-the-Middle)
Loading comments 0%