Logo
-

Byte Open Security

(ByteOS Network)

Log In

Sign Up

ByteOS

Security
Vulnerability Details
Registries
Custom Views
Weaknesses
Attack Patterns
Filters & Tools
CAPEC-600:Credential Stuffing
Attack Pattern ID:600
Version:v3.9
Attack Pattern Name:Credential Stuffing
Abstraction:Standard
Status:Stable
Likelihood of Attack:High
Typical Severity:High
DetailsContent HistoryRelated WeaknessesReports
▼Description

An adversary tries known username/password combinations against different systems, applications, or services to gain additional authenticated access. Credential Stuffing attacks rely upon the fact that many users leverage the same username/password combination for multiple systems, applications, and services.

▼Extended Description

Attacks of this kind often target management services over commonly used ports such as SSH, FTP, Telnet, LDAP, Kerberos, MySQL, and more. Additional targets include Single Sign-On (SSO) or cloud-based applications/services that utilize federated authentication protocols, and externally facing applications.

The primary goal of Credential Stuffing is to achieve lateral movement and gain authenticated access to additional systems, applications, and/or services. A successfully executed Credential Stuffing attack could result in the adversary impersonating the victim or executing any action that the victim is authorized to perform.

Although not technically a brute force attack, Credential Stuffing attacks can function as such if an adversary possess multiple known passwords for the same user account. This may occur in the event where an adversary obtains user credentials from multiple sources or if the adversary obtains a user's password history for an account.

Credential Stuffing attacks are similar to Password Spraying attacks (CAPEC-565) regarding their targets and their overall goals. However, Password Spraying attacks do not have any insight into known username/password combinations and instead leverage common or expected passwords. This also means that Password Spraying attacks must avoid inducing account lockouts, which is generally not a worry of Credential Stuffing attacks. Password Spraying attacks may additionally lead to Credential Stuffing attacks, once a successful username/password combination is discovered.

▼Alternate Terms
▼Relationships
NatureTypeIDName
ChildOfM560Use of Known Domain Credentials
CanFollowD16Dictionary-based Password Attack
CanFollowS49Password Brute Forcing
CanFollowS50Password Recovery Exploitation
CanFollowD55Rainbow Table Password Cracking
CanFollowD70Try Common or Default Usernames and Passwords
CanFollowD101Server Side Include (SSI) Injection
CanFollowD565Password Spraying
CanFollowD568Capture Credentials via Keylogger
CanPrecedeM151Identity Spoofing
CanPrecedeS653Use of Known Operating System Credentials
Nature: ChildOf
Type: Meta
ID: 560
Name: Use of Known Domain Credentials
Nature: CanFollow
Type: Detailed
ID: 16
Name: Dictionary-based Password Attack
Nature: CanFollow
Type: Standard
ID: 49
Name: Password Brute Forcing
Nature: CanFollow
Type: Standard
ID: 50
Name: Password Recovery Exploitation
Nature: CanFollow
Type: Detailed
ID: 55
Name: Rainbow Table Password Cracking
Nature: CanFollow
Type: Detailed
ID: 70
Name: Try Common or Default Usernames and Passwords
Nature: CanFollow
Type: Detailed
ID: 101
Name: Server Side Include (SSI) Injection
Nature: CanFollow
Type: Detailed
ID: 565
Name: Password Spraying
Nature: CanFollow
Type: Detailed
ID: 568
Name: Capture Credentials via Keylogger
Nature: CanPrecede
Type: Meta
ID: 151
Name: Identity Spoofing
Nature: CanPrecede
Type: Standard
ID: 653
Name: Use of Known Operating System Credentials
▼Execution Flow
Explore
1.

Acquire known credentials

The adversary must obtain known credentials in order to access the target system, application, or service.

Technique
An adversary purchases breached username/password combinations or leaked hashed passwords from the dark web.
An adversary leverages a key logger or phishing attack to steal user credentials as they are provided.
An adversary conducts a sniffing attack to steal credentials as they are transmitted.
An adversary gains access to a database and exfiltrates password hashes.
An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.
2.

Determine target's password policy

Determine the password policies of the target system/application to determine if the known credentials fit within the specified criteria.

Technique
Determine minimum and maximum allowed password lengths.
Determine format of allowed passwords (whether they are required or allowed to contain numbers, special characters, etc., or whether they are allowed to contain words from the dictionary).
Determine account lockout policy (a strict account lockout policy will prevent brute force attacks if multiple passwords are known for a single user account).
Experiment
1.

Attempt authentication

Try each username/password combination until the target grants access.

Technique
Manually or automatically enter each username/password combination through the target's interface.
Exploit
1.

Impersonate

An adversary can use successful experiments or authentications to impersonate an authorized user or system or to laterally move within a system or application

Technique
2.

Spoofing

Malicious data can be injected into the target system or into a victim user's system by an adversary. The adversary can also pose as a legitimate user to perform social engineering attacks.

Technique
3.

Data Exfiltration

The adversary can obtain sensitive data contained within the system or application.

Technique
▼Prerequisites
The system/application uses one factor password based authentication, SSO, and/or cloud-based authentication.
The system/application does not have a sound password policy that is being enforced.
The system/application does not implement an effective password throttling mechanism.
The adversary possesses a list of known user accounts and corresponding passwords that may exist on the target.
▼Skills Required
Low

A Credential Stuffing attack is very straightforward.

▼Resources Required
A machine with sufficient resources for the job (e.g. CPU, RAM, HD).
A known list of username/password combinations.
A custom script that leverages the credential list to launch the attack.
▼Indicators
Many invalid login attempts are coming from the same machine (same IP address) or for multiple user accounts within short succession.
The login attempts use passwords that have been used previously by the user account in question.
Login attempts are originating from IP addresses or locations that are inconsistent with the user's normal IP addresses or locations.
▼Consequences
ScopeLikelihoodImpactNote
ConfidentialityAccess ControlAuthenticationN/AGain PrivilegesN/A
ConfidentialityAuthorizationN/ARead DataN/A
IntegrityN/AModify DataN/A
Scope: Confidentiality, Access Control, Authentication
Likelihood: N/A
Impact: Gain Privileges
Note: N/A
Scope: Confidentiality, Authorization
Likelihood: N/A
Impact: Read Data
Note: N/A
Scope: Integrity
Likelihood: N/A
Impact: Modify Data
Note: N/A
▼Mitigations
Leverage multi-factor authentication for all authentication services and prior to granting an entity access to the domain network.
Create a strong password policy and ensure that your system enforces this policy.
Ensure users are not reusing username/password combinations for multiple systems, applications, or services.
Do not reuse local administrator account credentials across systems.
Deny remote use of local admin credentials to log into domain systems.
Do not allow accounts to be a local administrator on more than one system.
Implement an intelligent password throttling mechanism. Care must be taken to assure that these mechanisms do not excessively enable account lockout attacks such as CAPEC-2.
Monitor system and domain logs for abnormal credential access.
▼Example Instances
▼Related Weaknesses
IDName
CWE-262Not Using Password Aging
CWE-263Password Aging with Long Expiration
CWE-307Improper Restriction of Excessive Authentication Attempts
CWE-308Use of Single-factor Authentication
CWE-309Use of Password System for Primary Authentication
CWE-522Insufficiently Protected Credentials
CWE-654Reliance on a Single Factor in a Security Decision
ID: CWE-262
Name: Not Using Password Aging
ID: CWE-263
Name: Password Aging with Long Expiration
ID: CWE-307
Name: Improper Restriction of Excessive Authentication Attempts
ID: CWE-308
Name: Use of Single-factor Authentication
ID: CWE-309
Name: Use of Password System for Primary Authentication
ID: CWE-522
Name: Insufficiently Protected Credentials
ID: CWE-654
Name: Reliance on a Single Factor in a Security Decision
▼Taxonomy Mappings
Taxonomy NameEntry IDEntry Name
ATTACK1110.004Brute Force:Credential Stuffing
OWASP AttacksN/ACredential stuffing
Taxonomy Name: ATTACK
Entry ID: 1110.004
Entry Name: Brute Force:Credential Stuffing
Taxonomy Name: OWASP Attacks
Entry ID: N/A
Entry Name: Credential stuffing
▼Notes
▼References
Reference ID: REF-567
Title: Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors
Author:
Publication:
Publisher:Cybersecurity and Infrastructure Security Agency (CISA)
Edition:
URL:https://www.us-cert.gov/ncas/alerts/TA18-086A
URL Date:2020-05-01
Day:27
Month:03
Year:2018
Reference ID: REF-568
Title: Credential stuffing
Author:
Publication:
Publisher:Open Web Application Security Project (OWASP)
Edition:
URL:https://owasp.org/www-community/attacks/Credential_stuffing
URL Date:2020-05-01
Day:N/A
Month:N/A
Year:N/A
Reference ID: REF-569
Title: JPMorgan Chase Hacking Affects 76 Million Households
Author: Jessica Silver-Greenberg, Matthew Goldstein, Nicole Perlroth
Publication:
Publisher:The New York Times
Edition:
URL:https://dealbook.nytimes.com/2014/10/02/jpmorgan-discovers-further-cyber-security-issues/
URL Date:2020-05-01
Day:02
Month:10
Year:2014
Details not found