| Home > CAPEC List > CAPEC-644: Use of Captured Hashes (Pass The Hash) (Version 3.9) |
|
When authenticating via LM or NTLM, an authenticating account's plaintext credentials are not required by the protocols for successful authentication. Instead, the hashed credentials are used to determine if an authentication attempt is valid. If an adversary can obtain an account's hashed credentials, the hash values can then be passed to a system or service to authenticate, without needing to brute-force the hashes to obtain their cleartext values. Successful Pass The Hash attacks result in the adversary fully authenticating as the targeted account, which can further allow the adversary to laterally move within the network, impersonate a legitimate user, and/or download/install malware to systems within the domain. This technique can be performed against any operating system that leverages the LM or NTLM protocols even if the operating system is not Windows-based, since these systems/accounts may still authenticate to a Windows domain.
Medium
High
| Nature | Type | ID | Name |
|---|---|---|---|
| ChildOf | Standard Attack PatternStandard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It is often seen as a singular piece of a fully executed attack. A standard attack pattern is meant to provide sufficient details to understand the specific technique and how it attempts to accomplish a desired goal. A standard level attack pattern is a specific type of a more abstract meta level attack pattern. | 653 | Use of Known Operating System Credentials |
| CanPrecede | Meta Attack PatternMeta Attack Pattern - A meta level attack pattern in CAPEC is a decidedly abstract characterization of a specific methodology or technique used in an attack. A meta attack pattern is often void of a specific technology or implementation and is meant to provide an understanding of a high level approach. A meta level attack pattern is a generalization of related group of standard level attack patterns. Meta level attack patterns are particularly useful for architecture and design level threat modeling exercises. | 151 | Identity Spoofing |
| CanPrecede | Meta Attack PatternMeta Attack Pattern - A meta level attack pattern in CAPEC is a decidedly abstract characterization of a specific methodology or technique used in an attack. A meta attack pattern is often void of a specific technology or implementation and is meant to provide an understanding of a high level approach. A meta level attack pattern is a generalization of related group of standard level attack patterns. Meta level attack patterns are particularly useful for architecture and design level threat modeling exercises. | 165 | File Manipulation |
| CanPrecede | Standard Attack PatternStandard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It is often seen as a singular piece of a fully executed attack. A standard attack pattern is meant to provide sufficient details to understand the specific technique and how it attempts to accomplish a desired goal. A standard level attack pattern is a specific type of a more abstract meta level attack pattern. | 545 | Pull Data from System Resources |
| CanPrecede | Meta Attack PatternMeta Attack Pattern - A meta level attack pattern in CAPEC is a decidedly abstract characterization of a specific methodology or technique used in an attack. A meta attack pattern is often void of a specific technology or implementation and is meant to provide an understanding of a high level approach. A meta level attack pattern is a generalization of related group of standard level attack patterns. Meta level attack patterns are particularly useful for architecture and design level threat modeling exercises. | 549 | Local Execution of Code |
| View Name | Top Level Categories |
|---|---|
| Domains of Attack | Software |
| Mechanisms of Attack | Subvert Access Control |
Acquire known Windows credential hash value pairs: The adversary must obtain known Windows credential hash value pairs of accounts that exist on the domain.
| Techniques |
|---|
| An adversary purchases breached Windows credential hash value pairs from the dark web. |
| An adversary conducts a sniffing attack to steal Windows credential hash value pairs as they are transmitted. |
| An adversary gains access to a Windows domain system/files and exfiltrates Windows credential hash value pairs. |
| An adversary examines outward-facing configuration and properties files to discover hardcoded Windows credential hash value pairs. |
Attempt domain authentication: Try each Windows credential hash value pair until the target grants access.
| Techniques |
|---|
| Manually or automatically enter each Windows credential hash value pair 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 the domain
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.
Data Exfiltration: The adversary can obtain sensitive data contained within domain systems or applications.
| Scope | Impact | Likelihood |
|---|---|---|
Confidentiality Access Control Authentication | Gain Privileges | |
Confidentiality Authorization | Read Data | |
Integrity | Modify Data |
| CWE-ID | Weakness Name |
|---|---|
| 522 | Insufficiently Protected Credentials |
| 836 | Use of Password Hash Instead of Password for Authentication |
| 308 | Use of Single-factor Authentication |
| 294 | Authentication Bypass by Capture-replay |
| 308 | Use of Single-factor Authentication |
| Entry ID | Entry Name |
|---|---|
| 1550.002 | Use Alternate Authentication Material:Pass The Hash |
| Submissions | ||
|---|---|---|
| Submission Date | Submitter | Organization |
| 2018年07月31日 (Version 2.12) | CAPEC Content Team | |
| Modifications | ||
| Modification Date | Modifier | Organization |
| 2020年07月30日 (Version 3.3) | CAPEC Content Team | The MITRE Corporation |
| Updated Consequences, Description, Example_Instances, Execution_Flow, Indicators, Likelihood_Of_Attack, Mitigations, Prerequisites, References, Related_Attack_Patterns, Related_Weaknesses, Resources_Required, Skills_Required, Taxonomy_Mappings | ||
| 2022年02月22日 (Version 3.7) | CAPEC Content Team | The MITRE Corporation |
| Updated Description, Extended_Description | ||
| 2022年09月29日 (Version 3.8) | CAPEC Content Team | The MITRE Corporation |
| Updated Description | ||
|
Use of the Common Attack Pattern Enumeration and Classification (CAPEC), and the associated references from this website are subject to the Terms of Use. Copyright © 2007–2025, The MITRE Corporation. CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. |
||