Emulating Shellcodes - Chapter 2
Lets check different Cobalt Strike shellcodes and stages in the shellcodes emulator SCEMU.
This stages are fully emulated well and can get the IOC and the behavior of the shellcode.
But lets see another first stage big shellcode with c runtime embedded in a second stage.
In this case is loading tons of API using GetProcAddress at the beginning, then some encode/decode pointer and tls get/set values to store an address. And ends up crashing because is jumping an address that seems more code than address 0x9090f1eb.
Here there are two types of allocations:
Lets spawn a console on -c 3307548 and see if some of this allocations has the next stage.
The "m" command show all the memory maps but the "ma" show only the allocations done by the shellcode.
Dumping memory with "md" we see that there is data, and dissasembling this address with "d" we see the prolog of a function.
So we have second stage unpacked in alloc_e40064
With "mdd" we do a memory dump to disk we found the size in previous screenshot, and we can do some static reversing of stage2 in radare/ghidra/ida
In radare we can verify that the extracted is the next stage:
I usually do correlation between the emulation and ghidra, to understand the algorithms.
If wee look further we can realize that the emulator called a function on the stage2, we can see the change of code base address and is calling the allocated buffer in 0x4f...
And this stage2 perform several API calls let's check it in ghidra.
We can see in the emulator that enters in the IF block, and what are the (*DAT_...)() calls
Before a crash lets continue to the SEH pointer, in this case is the way, and the exception routine checks IsDebuggerPresent() which is not any debugger pressent for sure, so eax = 0;
So lets say yes and continue the emulation.
Both IsDebuggerPresent() and UnHandledExceptionFilter() can be used to detect a debugger, but the emulator return what has to return to not be detected.
Nevertheless the shellcode detects something and terminates the process.
Lets trace the branches to understand the logic:
target/release/scemu -f shellcodes/unsuported_cs.bin -vv | egrep '(\*\*|j|cmp|test)'
Lets see from the console where is pointing the SEH chain item:
to be continued ...
https://github.com/sha0coder/scemu
Related word
- Hack Apps
- Pentest Tools Kali Linux
- Pentest Tools Port Scanner
- Nsa Hack Tools Download
- Hackrf Tools
- Hacker Tools Free Download
- Hacking App
- Pentest Tools Open Source
- Top Pentest Tools
- Usb Pentest Tools
- Hacker Tools Software
- Hack Tools Pc
- Hacker Search Tools
- Game Hacking
- Ethical Hacker Tools
- Pentest Tools Online
- Hacking Tools Usb
- Pentest Tools Download
- Hacking Tools For Windows Free Download
- New Hacker Tools
- Pentest Box Tools Download
- Hacking Tools Download
- Hacker Tools 2020
- Ethical Hacker Tools
- Hack Apps
- How To Hack
- Hacking Tools Usb
- How To Make Hacking Tools
- Termux Hacking Tools 2019
- Hacking Tools For Windows
- Hacker Search Tools
- Hacking App
- Hacker Tools List
- Hacker Tools List
- Hack Tools
- Hack Tool Apk
- Hacker Tools List
- Github Hacking Tools
- Hacker Tools Apk Download
- Pentest Tools Subdomain
- Pentest Tools Github
- Pentest Tools Free
- Hacking Tools Download
- Usb Pentest Tools
- Nsa Hack Tools
- What Are Hacking Tools
- Pentest Tools Bluekeep
- Hacking Tools Pc
- Hacking Tools Free Download
- How To Install Pentest Tools In Ubuntu
- Tools 4 Hack
- How To Hack
- Pentest Tools Android
- Hacker Search Tools
- Best Hacking Tools 2020
- Hacker Security Tools
- Hacker Tools Free Download
- Blackhat Hacker Tools
- New Hacker Tools
- Physical Pentest Tools
- Hacker Tools Apk
- What Are Hacking Tools
- Hack Website Online Tool
- Github Hacking Tools
- Pentest Tools Url Fuzzer
- Hacker Security Tools
- Tools Used For Hacking
- Pentest Tools
- Hack Tools
- Top Pentest Tools
0 条评论:
发表评论
订阅 博文评论 [Atom]
<< 主页