Accessibility Features

From ATT&CK
Jump to: navigation, search
Accessibility Features
Technique
ID T1015
Tactic Persistence, Privilege Escalation
Platform Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows XP, Windows 7, Windows 8, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, Windows Vista, Windows 8.1
Permissions Required Administrator
Effective Permissions SYSTEM
Data Sources Windows Registry, File monitoring, Process monitoring
CAPEC ID CAPEC-558

Windows contains accessibility features that may be launched with a key combination before a user has logged in (for example, when the user is on the Windows logon screen). An adversary can modify the way these programs are launched to get a command prompt or backdoor without logging in to the system.

Two of these accessibility programs are C:\Windows\System32\utilman.exe, launched when the Windows + U key combination is pressed, and C:\Windows\System32\sethc.exe, launched when the shift key is pressed five times. The program "sethc.exe" is often referred to as sticky keys, and has been used by adversaries for unauthenticated access through a remote desktop login screen.1

Depending on the version of Windows, an adversary may take advantage of these features in different ways:

On Windows XP and Windows Server 2003/R2, the program (e.g., C:\Windows\System32\utilman.exe) may be replaced with "cmd.exe" (or another program that provides backdoor access). Subsequently, pressing the appropriate key combination at the login screen while sitting at the keyboard or when connected over Remote Desktop Protocol will cause the replaced file to be executed with SYSTEM privileges.2

On Windows Vista and later as well as Windows Server 2008 and later, a Registry key may be modified that configures "cmd.exe," or another program that provides backdoor access, as a "debugger" for the accessibility program (e.g., "utilman.exe"). After the Registry is modified, pressing the appropriate key combination at the login screen while at the keyboard or when connected with RDP will cause the "debugger" program to be executed with SYSTEM privileges.2

Examples

  • Axiom actors have been known to use the Sticky Keys replacement within RDP sessions to obtain persistence.3
  • Deep Panda has used the sticky-keys technique to bypass the RDP login screen on remote systems during intrusions.4
  • APT29 used sticky-keys to obtain unauthenticated, privileged console access.5
  • PinchDuke collects user files from the compromised host.6

Mitigation

To use this technique remotely, an adversary must use it in conjunction with RDP. Ensure that Network Level Authentication is enabled to force the remote desktop session to authenticate before the session is created and the login screen displayed. It is enabled by default on Windows Vista and later.7

If possible, use a Remote Desktop Gateway to manage connections and security configuration of RDP within a network.8

Identify and block potentially malicious software that may be executed by an adversary with this technique by using whitelisting9 tools, like AppLocker,1011 or Software Restriction Policies12 where appropriate.13

Detection

Changes to accessibility utility binaries or binary paths that do not correlate with known software, patch cycles, etc., are suspicious. Command line invocation of tools capable of modifying the Registry for associated keys are also suspicious. Utility arguments and the binaries themselves should be monitored for changes. Monitor Registry keys within HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options.

References