CAPECattack pattern

CAPEC-644 Use of Captured Hashes (Pass The Hash)

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

Description

An adversary obtains (i.e. steals or purchases) legitimate Windows domain credential hash values to access systems within the domain that leverage the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols.

Extended description

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.

Execution flow

1. [Explore] [Acquire known Windows credential hash value pairs] The adversary must obtain known Windows credential hash value pairs of accounts that exist on the domain. 2. [Experiment] [Attempt domain authentication] Try each Windows credential hash value pair 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 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.

Prerequisites

• The system/application is connected to the Windows domain. • The system/application leverages the Lan Man (LM) and/or NT Lan Man (NTLM) authentication protocols. • The adversary possesses known Windows credential hash value pairs that exist on the target domain.

Skills required

• [Low] Once an adversary obtains a known Windows credential hash value pair, leveraging it is trivial.

Consequences

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

Mitigations

• Prevent the use of Lan Man and NT Lan Man authentication on severs and apply patch KB2871997 to Windows 7 and higher systems. • Leverage multi-factor authentication for all authentication services and prior to granting an entity access to the domain network. • Monitor system and domain logs for abnormal credential access. • Create a strong password policy and ensure that your system enforces this policy. • Leverage system penetration testing and other defense in depth methods to determine vulnerable systems within a domain.

Related

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

Can precede · CAPEC (4)

  • CAPEC-151 Identity Spoofing attack pattern
  • CAPEC-165 File Manipulation attack pattern
  • CAPEC-545 Pull Data from System Resources attack pattern
  • CAPEC-549 Local Execution of Code attack pattern

Child of · CAPEC (1)

  • CAPEC-653 Use of Known Operating System Credentials attack pattern

Weakness · CWE (4)

  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-836 Use of Password Hash Instead of Password for Authentication weakness

Referenced by CWE · attack pattern (4)

  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-308 Use of Single-factor Authentication weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-836 Use of Password Hash Instead of Password for Authentication weakness