| Name |
Use of Known Windows Credentials |
|
| Likelyhood of attack |
Typical severity |
| High |
High |
|
| Summary |
An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows domain credentials (e.g. userID/password) to achieve authentication and to perform authorized actions on the domain, under the guise of an authenticated user or service. Attacks leveraging trusted Windows credentials typically result in the adversary laterally moving within the local Windows network, since users are often allowed to login to systems/applications within the domain using their Windows domain password. This domain authentication can occur directly (user typing in their password or PIN) or via Single Sign-On (SSO) or cloud-based authentication, which often don't verify the authenticity of the user's input. |
| Prerequisites |
The system/application is connected to the Windows domain. 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 Windows user accounts and corresponding passwords that may exist on the target. |
| Execution Flow |
| Step |
Phase |
Description |
Techniques |
| 1 |
Explore |
[Acquire known Windows credentials] The adversary must obtain known Windows credentials in order to access the target system, application, or service within the domain. |
- An adversary purchases breached Windows 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 Windows credentials as they are transmitted.
- An adversary gains access to a Windows domain system/files and exfiltrates Windows password hashes.
- An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credentials.
|
| 2 |
Experiment |
[Attempt domain authentication] Try each Windows credential against various systems, applications, and services within the domain until the target grants access. |
- 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 domain |
|
| 4 |
Exploit |
[Spoofing] Malicious data can be injected into the target system or into other systems on the domain. The adversary can also pose as a legitimate domain user to perform social engineering attacks. |
|
| 5 |
Exploit |
[Data Exfiltration] The adversary can obtain sensitive data contained within domain systems or applications. |
|
|
| Solutions | 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 |
|
CWE ID
|
Description
|
| CWE-262 |
Not Using Password Aging |
| CWE-263 |
Password Aging with Long Expiration |
| CWE-307 |
Improper Restriction of Excessive Authentication Attempts |
| CWE-308 |
Use of Single-factor Authentication |
| CWE-309 |
Use of Password System for Primary Authentication |
| CWE-522 |
Insufficiently Protected Credentials |
| CWE-654 |
Reliance on a Single Factor in a Security Decision |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-151 |
Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials. |
| CAPEC-560 |
An adversary guesses or obtains (i.e. steals or purchases) legitimate credentials (e.g. userID/password) to achieve authentication and to perform authorized actions under the guise of an authenticated user or service. |
|