CAPECattack pattern

CAPEC-70 Try Common or Default Usernames and Passwords

High Official page ↗
Abstraction
Detailed
Status
Draft
Likelihood of attack
Medium
Typical severity
High
CAPEC version
3.9

Description

An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.

Prerequisites

• The system uses one factor password based authentication.The adversary has the means to interact with the system.

Skills required

• [Low] An adversary just needs to gain access to common default usernames/passwords specific to the technologies used by the system. Additionally, a brute force attack leveraging common passwords can be easily realized if the user name is known.

Consequences

• Confidentiality, Access Control, Authorization: Gain Privileges

Mitigations

• Delete all default account credentials that may be put in by the product vendor. • Implement a password throttling mechanism. This mechanism should take into account both the IP address and the log in name of the user. • Put together a strong password policy and make sure that all user created passwords comply with it. Alternatively automatically generate strong passwords for users. • Passwords need to be recycled to prevent aging, that is every once in a while a new password must be chosen.

Related

Att&ck technique · MITRE ATT&CK (1)

Can precede · CAPEC (5)

  • CAPEC-151 Identity Spoofing attack pattern
  • CAPEC-560 Use of Known Domain Credentials attack pattern
  • CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
  • CAPEC-600 Credential Stuffing attack pattern
  • CAPEC-653 Use of Known Operating System Credentials attack pattern

Child of · CAPEC (1)

  • CAPEC-49 Password Brute Forcing attack pattern

Weakness · CWE (7)

  • CWE-262 Not Using Password Aging weakness
  • CWE-263 Password Aging with Long Expiration weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-309 Use of Password System for Primary Authentication weakness
  • CWE-521 Weak Password Requirements weakness
  • CWE-654 Reliance on a Single Factor in a Security Decision weakness
  • CWE-798 Use of Hard-coded Credentials weakness

Referenced by CAPEC · can follow (1)

  • CAPEC-700 Network Boundary Bridging attack pattern

Referenced by CWE · attack pattern (7)

  • CWE-262 Not Using Password Aging weakness
  • CWE-263 Password Aging with Long Expiration weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-309 Use of Password System for Primary Authentication weakness
  • CWE-521 Weak Password Requirements weakness
  • CWE-654 Reliance on a Single Factor in a Security Decision weakness
  • CWE-798 Use of Hard-coded Credentials weakness