Ctrl+Inject

Created the Saturday 23 March 2019. Updated 2 months, 1 week ago.

The "Control Signal Handler Callback" technique involves injecting malicious code into a process by using a callback function for control signal handlers. When a control signal, such as Ctrl+C, is received by a process, the system creates a new thread to execute a function to handle the signal. This thread is typically created by the legitimate process "csrss.exe" in the system, making it more difficult to detect the injected code.

To successfully implement this technique, it is necessary to bypass certain Windows protections such as Pointer Encoding and Control Flow Guard. Pointer encoding is used to protect against pointer corruption, and the technique involves reproducing the encoding to appear legitimate. Control Flow Guard is a security mechanism that prevents memory corruption, such as buffer overflow, and the technique uses the API SetProcessValidCallTargets to validate the call target. By triggering a control signal, the injected code is executed.

Here is a general outline of the process of injecting code using control signal handlers and callback functions:

Determine the address of the callback function for control signals in the target process.
Create a trampoline function that will be used to execute the original code from the callback function after the injection has been applied.
Calculate the relative address of the trampoline function and store it in a jump instruction.
Overwrite the callback function with the jump instruction and the address of the injected code.
Modify the injected code to transfer control back to the trampoline function after executing the desired processing.
Trigger a control signal, such as Ctrl+C, in the target process to execute the injected code.

Technique Identifier

U1213

Technique Tags

callback function control signal process system thread csrss.exe detection injection code console process pointer encoding Control Flow Guard memory corruption buffer overflow SetProcessValidCallTargets

Featured Windows API's

Below, you will find a list of the most commonly used Windows API's that are currently utilized by malware authors for current evasion technique. This list is meant to provide an overview of the API's that are commonly used for this purpose. If there are any API's that you feel should be included on this list, please do not hesitate to contact us. We will be happy to update the list and provide any additional information or documentation that may be helpful.

GetCurrentProcess

Code Snippets

Description

This code first defines a callback function called ControlSignalHandler that will be used to inject malicious code. It then bypasses pointer encoding and control flow guard to ensure that the function can be called. Finally, it sets the callback function for control signal handlers using the SetConsoleCtrlHandler function and triggers a control signal by calling GenerateConsoleCtrlEvent.

#include <Windows.h>
#include <cstdio>

// callback function for control signal handlers
BOOL WINAPI ControlSignalHandler(DWORD dwCtrlType)
{
    // inject malicious code here

    return TRUE;
}

int main()
{
    // bypass pointer encoding
    void* encodedPointer = EncodePointer((PVOID)ControlSignalHandler);
    void* decodedPointer = DecodePointer(encodedPointer);

    // bypass control flow guard
    SetProcessValidCallTargets(GetCurrentProcess(), (UINT_PTR)decodedPointer, sizeof(void*));

    // set callback function for control signal handlers
    SetConsoleCtrlHandler((PHANDLER_ROUTINE)decodedPointer, TRUE);

    // trigger control signal (Ctrl+C)
    GenerateConsoleCtrlEvent(CTRL_C_EVENT, 0);

    return 0;
}

Additional Resources

External Links

The resources provided below are associated links that will give you even more detailed information and research on current evasion technique. It is important to note that, while these resources may be helpful, it is important to exercise caution when following external links. As always, be careful when clicking on links from unknown sources, as they may lead to malicious content.

Fortinet Blog - Broad, Integrated, Automated Cybersecurity