CAPEC-600 Detail

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.

Execution Flow

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

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

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

• 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).

[Attempt authentication] Try each username/password combination until the target grants access.

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

[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

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

[Data Exfiltration] The adversary can obtain sensitive data contained within the system or application.

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

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.

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.

Related Weaknesses

References

REF-567

Alert (TA18-086A): Brute Force Attacks Conducted by Cyber Actors
https://www.us-cert.gov/ncas/alerts/TA18-086A

REF-568

Credential stuffing
https://owasp.org/www-community/attacks/Credential_stuffing

REF-569

JPMorgan Chase Hacking Affects 76 Million Households
Jessica Silver-Greenberg, Matthew Goldstein, Nicole Perlroth.
https://dealbook.nytimes.com/2014/10/02/jpmorgan-discovers-further-cyber-security-issues/

Submission

Modifications