Adversaries may gather credential material by invoking or forcing a user to automatically provide authentication information through a mechanism in which they can intercept.
The Server Message Block (SMB) protocol is commonly used in Windows networks for authentication and communication between systems for access to resources and file sharing. When a Windows system attempts to connect to an SMB resource it will automatically attempt to authenticate and send credential information for the current user to the remote system. (Citation: Wikipedia Server Message Block) This behavior is typical in enterprise environments so that users do not need to enter credentials to access network resources.
Web Distributed Authoring and Versioning (WebDAV) is also typically used by Windows systems as a backup protocol when SMB is blocked or fails. WebDAV is an extension of HTTP and will typically operate over TCP ports 80 and 443. (Citation: Didier Stevens WebDAV Traffic) (Citation: Microsoft Managing WebDAV Security)
Adversaries may take advantage of this behavior to gain access to user account hashes through forced SMB/WebDAV authentication. An adversary can send an attachment to a user through spearphishing that contains a resource link to an external server controlled by the adversary (i.e. Template Injection), or place a specially crafted file on navigation path for privileged accounts (e.g. .SCF file placed on desktop) or on a publicly accessible share to be accessed by victim(s). When the user's system accesses the untrusted resource it will attempt authentication and send information, including the user's hashed credentials, over SMB to the adversary controlled server. (Citation: GitHub Hashjacking) With access to the credential hash, an adversary can perform off-line Brute Force cracking to gain access to plaintext credentials. (Citation: Cylance Redirect to SMB)
There are several different ways this can occur. (Citation: Osanda Stealing NetNTLM Hashes) Some specifics from in-the-wild use include:
Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name |
---|---|---|---|---|
AC-3 | Access Enforcement | Protects | T1187 | Forced Authentication |
AC-4 | Information Flow Enforcement | Protects | T1187 | Forced Authentication |
CA-7 | Continuous Monitoring | Protects | T1187 | Forced Authentication |
CM-2 | Baseline Configuration | Protects | T1187 | Forced Authentication |
CM-6 | Configuration Settings | Protects | T1187 | Forced Authentication |
CM-7 | Least Functionality | Protects | T1187 | Forced Authentication |
SC-7 | Boundary Protection | Protects | T1187 | Forced Authentication |
SI-10 | Information Input Validation | Protects | T1187 | Forced Authentication |
SI-15 | Information Output Filtering | Protects | T1187 | Forced Authentication |
SI-4 | System Monitoring | Protects | T1187 | Forced Authentication |
cloud_app_security_policies | Cloud App Security Policies | technique_scores | T1187 | Forced Authentication |
cloud_app_security_policies | Cloud App Security Policies | technique_scores | T1187 | Forced Authentication |