CAPEC-653

Use of Known Operating System Credentials
Haute
Haute
Draft
2020-07-30
00h00 +00:00
2022-09-29
00h00 +00:00
Alerte pour un CAPEC
Restez informé de toutes modifications pour un CAPEC spécifique.
Gestion des notifications

Descriptions du CAPEC

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.

Informations du CAPEC

Flux d'exécution

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.

Technique
  • An adversary purchases breached operating system 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 operating system credentials as they are transmitted.
  • An adversary gains access to a system/files and exfiltrates password hashes.
  • An adversary examines outward-facing configuration and properties files to discover hardcoded credentials.
2) Experiment

[Attempt authentication] Try each operating system credential against various systems, applications, and services within the domain until the target grants access.

Technique
  • Manually or automatically enter each credential through the target's interface.
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.

Conditions préalables

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.

Compétences requises

Once an adversary obtains a known credential, leveraging it is trivial.

Ressources nécessaires

A list of known credentials for the targeted domain.
A custom script that leverages a credential list to launch an attack.

Atténuations

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.

Faiblesses connexes

CWE-ID Nom de la faiblesse

CWE-522

Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

CWE-307

Improper Restriction of Excessive Authentication Attempts
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

CWE-308

Use of Single-factor Authentication
The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme.

CWE-309

Use of Password System for Primary Authentication
The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism.

CWE-262

Not Using Password Aging
The product does not have a mechanism in place for managing password aging.

CWE-263

Password Aging with Long Expiration
The product supports password aging, but the expiration period is too long.

CWE-654

Reliance on a Single Factor in a Security Decision
A protection mechanism relies exclusively, or to a large extent, on the evaluation of a single condition or the integrity of a single object or entity in order to make a decision about granting access to restricted resources or functionality.

Références

REF-575

Attackers can use Zoom to steal users’ Windows credentials with no warning
Dan Goodin.
https://arstechnica.com/information-technology/2020/04/unpatched-zoom-bug-lets-attackers-steal-windows-credentials-with-no-warning/

REF-576

How Attackers are Stealing Your Credentials with Mimikatz
Jeff Warren.
https://blog.stealthbits.com/how-attackers-are-stealing-your-credentials-with-mimikatz/

Soumission

Nom Organisation Date Date de publication
CAPEC Content Team The MITRE Corporation 2020-07-30 +00:00

Modifications

Nom Organisation Date Commentaire
CAPEC Content Team The MITRE Corporation 2022-02-22 +00:00 Updated Description, Extended_Description
CAPEC Content Team The MITRE Corporation 2022-09-29 +00:00 Updated @Name, Description, Execution_Flow, Extended_Description, Mitigations, Prerequisites, Resources_Required, Skills_Required