Isabel Tuson
63 lines
4.8 KiB
JSON
63 lines
4.8 KiB
JSON
{
|
|
"type": "bundle",
|
|
"id": "bundle--92d9ea00-b12b-45b9-9e1a-bc8019a31162",
|
|
"spec_version": "2.0",
|
|
"objects": [
|
|
{
|
|
"external_references": [
|
|
{
|
|
"source_name": "mitre-attack",
|
|
"external_id": "T1055.012",
|
|
"url": "https://attack.mitre.org/techniques/T1055/012"
|
|
},
|
|
{
|
|
"url": "http://www.autosectools.com/process-hollowing.pdf",
|
|
"description": "Leitch, J. (n.d.). Process Hollowing. Retrieved November 12, 2014.",
|
|
"source_name": "Leitch Hollowing"
|
|
},
|
|
{
|
|
"url": "https://www.endgame.com/blog/technical-blog/ten-process-injection-techniques-technical-survey-common-and-trending-process",
|
|
"description": "Hosseini, A. (2017, July 18). Ten Process Injection Techniques: A Technical Survey Of Common And Trending Process Injection Techniques. Retrieved December 7, 2017.",
|
|
"source_name": "Endgame Process Injection July 2017"
|
|
}
|
|
],
|
|
"object_marking_refs": [
|
|
"marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168"
|
|
],
|
|
"created_by_ref": "identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5",
|
|
"name": "Process Hollowing",
|
|
"description": "Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process. \n\nProcess hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as <code>CreateProcess</code>, which includes a flag to suspend the processes primary thread. At this point the process can be unmapped using APIs calls such as <code>ZwUnmapViewOfSection</code> or <code>NtUnmapViewOfSection</code> before being written to, realigned to the injected code, and resumed via <code>VirtualAllocEx</code>, <code>WriteProcessMemory</code>, <code>SetThreadContext</code>, then <code>ResumeThread</code> respectively.(Citation: Leitch Hollowing)(Citation: Endgame Process Injection July 2017)\n\nThis is very similar to [Thread Local Storage](https://attack.mitre.org/techniques/T1055/005) but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process. ",
|
|
"id": "attack-pattern--b200542e-e877-4395-875b-cf1a44537ca4",
|
|
"type": "attack-pattern",
|
|
"kill_chain_phases": [
|
|
{
|
|
"kill_chain_name": "mitre-attack",
|
|
"phase_name": "defense-evasion"
|
|
},
|
|
{
|
|
"kill_chain_name": "mitre-attack",
|
|
"phase_name": "privilege-escalation"
|
|
}
|
|
],
|
|
"modified": "2020-06-20T22:28:08.758Z",
|
|
"created": "2020-01-14T17:21:54.470Z",
|
|
"x_mitre_defense_bypassed": [
|
|
"Application control",
|
|
"Anti-virus"
|
|
],
|
|
"x_mitre_data_sources": [
|
|
"Process monitoring",
|
|
"API monitoring"
|
|
],
|
|
"x_mitre_permissions_required": [
|
|
"User"
|
|
],
|
|
"x_mitre_detection": "Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as <code>CreateRemoteThread</code>, <code>SuspendThread</code>/<code>SetThreadContext</code>/<code>ResumeThread</code>, and those that can be used to modify memory within another process, such as <code>VirtualAllocEx</code>/<code>WriteProcessMemory</code>, may be used for this technique.(Citation: Endgame Process Injection July 2017)\n\nAnalyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. ",
|
|
"x_mitre_version": "1.0",
|
|
"x_mitre_is_subtechnique": true,
|
|
"x_mitre_platforms": [
|
|
"Windows"
|
|
]
|
|
}
|
|
]
|
|
} |