One way to use the shellshock.h header is to:
- Create a 'Shellshock' object
- Resolve functions that you intend to use with the 'load_' member functions
- Utilize a singular function and make sure that all variables are created
on the stack
Once something like this is achieved, you can compile the binary to an object
file and dump the .text
section out to a whatever you like. That dump should
be position independent.
git clone https://github.com/0xvpr/vpr-shell-shock.git
cd vpr-shell-shock
cmake -DCMAKE_INSTALL_PREFIX=/your/desired/path/ -B build
cmake --install build
#set( CMAKE_C_STANDARD 99 ) # at least c99 if using c
#set( CMAKE_CXX_STANDARD 17 ) # at least c++17 if using cpp
include(FetchContent)
FetchContent_Declare(
vpr-shell-shock
GIT_REPOSITORY https://github.com/0xvpr/vpr-shell-shock.git
GIT_TAG main # Or use a specific version tag like "v1.0.0"
)
FetchContent_MakeAvailable(vpr-shell-shock)
add_executable(app main.cpp)
target_link_libraries(app PRIVATE vpr-shell-shock::shell-shock)
#include "vpr/shellshock.h"
typedef int (WINAPI * MessageBoxA_t)(HWND, LPCSTR, LPCSTR, UINT);
extern "C" int payload_cpp(void) {
auto ss = vpr::ss::shellshock();
// Load target function into a temporary variable.
char szMessageBoxA[] = "MessageBoxA";
auto fMessageBoxA = ss.find_user32_func<MessageBoxA_t>(szMessageBoxA);
// Perform function call
char szTitle[] = "Shellshock";
char szMessage[] = "Success.";
fMessageBoxA && fMessageBoxA(nullptr, szMessage, szTitle, 0);
return 0;
}
If you are using MinGW and you want the payload to be immediately exported to a file,
you can do the following:
// Payload that will be exported to shellcode
extern "C" auto payload() noexcept -> void { (...) }
// Immediately after the function ends
void stub() {
return;
}
int main() {
auto pd = ss::payload_data::build_from_payload(payload, stub);
pd.extract_to_file("shellcode.bin");
}
Compiling this code to an executable should export the code to the specified
file location.
Compiling this code to an object should mean that the payload
function of
the .text
section is out new position independent executable.
NOTE: Compilation may fail if position-independent-code is not enabled AND/OR if function sections are enabled.