MITRE ATT&CKsub-technique
T1055.011 Extra Window Memory Injection
- Domain
- enterprise
- Tactics
- Stealth, Privilege Escalation
- Platforms
- Windows
- Version
- 2.0
- Created
- 2020-01-14
Description
Adversaries may inject malicious code into process via Extra Window Memory (EWM) in order to evade process-based defenses as well as possibly elevate privileges. EWM injection is a method of executing arbitrary code in the address space of a separate live process.
Before creating a window, graphical Windows-based processes must prescribe to or register a windows class, which stipulate appearance and behavior (via windows procedures, which are functions that handle input/output of data). Registration of new windows classes can include a request for up to 40 bytes of EWM to be appended to the allocated memory of each instance of that class. This EWM is intended to store data specific to that window and has specific application programming interface (API) functions to set and get its value.
Although small, the EWM is large enough to store a 32-bit pointer and is often used to point to a windows procedure. Malware may possibly utilize this memory location in part of an attack chain that includes writing code to shared sections of the process’s memory, placing a pointer to the code in EWM, then invoking execution by returning execution control to the address in the process’s EWM.
Execution granted through EWM injection may allow access to both the target process's memory and possibly elevated privileges. Writing payloads to shared sections also avoids the use of highly monitored API calls such as WriteProcessMemory and CreateRemoteThread. More sophisticated malware samples may also potentially bypass protection mechanisms such as data execution prevention (DEP) by triggering a combination of windows procedures and other system functions that will rewrite the malicious payload inside an executable portion of the target process.
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via EWM injection may also evade detection from security products since the execution is masked under a legitimate process.
Related
Subtechnique of · MITRE ATT&CK (1)
- T1055 Process Injection technique
Referenced by MITRE ATT&CK · mitigates (1)
- M1040 Behavior Prevention on Endpoint mitigation
Referenced by MITRE ATT&CK · uses (2)
Referenced by Compliance · mitigates (7)
- CIS-13.7 Deploy a Host-Based Intrusion Prevention Solution CIS Safeguard v8.1
- NIST-AC-6 Least Privilege NIST 800-53 control
- NIST-SC-18 Mobile Code NIST 800-53 control
- NIST-SC-7 Boundary Protection NIST 800-53 control
- NIST-SI-2 Flaw Remediation NIST 800-53 control
- NIST-SI-3 Malicious Code Protection NIST 800-53 control
- NIST-SI-4 System Monitoring NIST 800-53 control
References
- https://www.endgame.com/blog/technical-blog/ten-process-injection-techniques-technical-survey-common-and-trending-process Elastic Process Injection July 2017
- https://www.malwaretech.com/2013/08/powerloader-injection-something-truly.html MalwareTech Power Loader Aug 2013
- https://www.welivesecurity.com/2013/03/19/gapz-and-redyms-droppers-based-on-power-loader-code/ WeLiveSecurity Gapz and Redyms Mar 2013
- https://msdn.microsoft.com/library/windows/desktop/ms633574.aspx Microsoft Window Classes
- https://msdn.microsoft.com/library/windows/desktop/ms633584.aspx Microsoft GetWindowLong function
- https://msdn.microsoft.com/library/windows/desktop/ms633591.aspx Microsoft SetWindowLong function