CAPECattack pattern

CAPEC-653 Use of Known Operating System Credentials

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

Description

An adversary guesses or obtains (i.e. steals or purchases) legitimate operating system credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the system, under the guise of an authenticated user or service. This applies to any Operating System.

Extended description

This attack can be extremely harmful when the operating system credentials used are for a root or admin user. Once an adversary gains access using credentials with elevated privileges, they are free to alter important system files which can effect other users who may use the system or other users on the system's network.

Execution flow

1. [Explore] [Acquire known operating system credentials] The adversary must obtain known operating system credentials in order to access the target system, application, or service within the domain. 2. [Experiment] [Attempt authentication] Try each operating system credential against various systems, applications, and services within the domain until the target grants access. 3. [Exploit] [Impersonate] An adversary can use successful experiments or authentications to impersonate an authorized user or system, or to laterally move within the network 4. [Exploit] [Spoofing] Malicious data can be injected into the target system or into other systems on the network. The adversary can also pose as a legitimate user to perform social engineering attacks. 5. [Exploit] [Data Exfiltration] The adversary can obtain sensitive data contained within system files or application configuration.

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] Once an adversary obtains a known credential, leveraging it is trivial.

Consequences

• Confidentiality, Access Control, Authentication: Gain Privileges • Confidentiality, Authorization: Read Data • Integrity: Modify Data

Mitigations

• Leverage multi-factor authentication for all authentication services and prior to granting an entity access to the 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

Can precede · CAPEC (1)

Child of · CAPEC (1)

  • CAPEC-560 Use of Known Domain Credentials attack pattern

Weakness · CWE (7)

  • CWE-262 Not Using Password Aging weakness
  • CWE-263 Password Aging with Long Expiration weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-309 Use of Password System for Primary Authentication weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-654 Reliance on a Single Factor in a Security Decision weakness

Referenced by CAPEC · can precede (8)

  • CAPEC-16 Dictionary-based Password Attack attack pattern
  • CAPEC-49 Password Brute Forcing attack pattern
  • CAPEC-50 Password Recovery Exploitation attack pattern
  • CAPEC-55 Rainbow Table Password Cracking attack pattern
  • CAPEC-565 Password Spraying attack pattern
  • CAPEC-568 Capture Credentials via Keylogger attack pattern
  • CAPEC-600 Credential Stuffing attack pattern
  • CAPEC-70 Try Common or Default Usernames and Passwords attack pattern

Referenced by CAPEC · child of (2)

  • CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
  • CAPEC-644 Use of Captured Hashes (Pass The Hash) attack pattern

Referenced by CWE · attack pattern (7)

  • CWE-262 Not Using Password Aging weakness
  • CWE-263 Password Aging with Long Expiration weakness
  • CWE-307 Improper Restriction of Excessive Authentication Attempts weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-309 Use of Password System for Primary Authentication weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-654 Reliance on a Single Factor in a Security Decision weakness