DDexec – A Technique To Run Binaries Filelessly And Stealthily On Linux Using Dd To Replace The Shell With Another Process
In Linux in order to run a program it must exist as a file, it must be accessible in some way through the file system hierarchy (this is just how
execve() works). This file may reside on disk or in ram (tmpfs, memfd) but you need a filepath. This has made very easy to control what is run on a Linux system, it makes easy to detect threats and attacker’s tools or to prevent them from trying to execute anything of theirs at all (e. g. not allowing unprivileged users to place executable files anywhere).
But this technique is here to change all of this. If you can not start the process you want… then you hijack one already existing.
Pipe into the
ddexec.sh script the base64 of the binary you want to run (without newlines). The arguments for the script are the arguments for the program (starting with
Here, try this:
base64 -w0 /bin/ls | bash ddexec.sh /bin/ls -lA
There is also the
ddsc.sh script that allows you to run binary code directly. The following is a “Hello world” shellcode.
bash ddsc.sh -x <<< "4831c0fec089c7488d3510000000ba0c0000000f054831c089c7b03c0f0548656c6c6f20776f726c640a00"
bash ddsc.sh < <(xxd -ps -r <<< "4831c0fec089c7488d3510000000ba0c0000000f054831c089c7b03c0f0548656c6c6f20776f726c640a00")
And yes. It works with meterpreter.
Tested Linux distributions are Debian, Alpine and Arch. Supported shells are bash, zsh and ash over x86_64 and aarch64 (arm64) architectures.
This script depends on the following tools to work.
dd bash | zsh | ash (busybox) head tail cut grep od readlink wc tr base64
If you are able to modify arbitrarily the memory of a process then you can take over it. This can be used to hijack an already existing process and replace it with another program. We can achieve this either by using the
ptrace() syscall (which requires you to have the ability to execute syscalls or to have gdb available on the system) or, more interestingly, writing to
/proc/$pid/mem is a one-to-one mapping of the entire address space of a process (e. g. from
0x7ffffffffffff000 in x86-64). This means that reading from or writing to this file at an offset
x is the same as reading from or modifying the contents at the virtual address
Now, we have four basic problems to face:
- In general, only root and the program owner of the file may modify it.
- If we try to read or write to an address not mapped in the address space of the program we will get an I/O error.
This problems have solutions that, although they are not perfect, are good:
- Most shell interpreters allow the creation of file descriptors that will then be inherited by child processes. We can create a fd pointing to the
memfile of the sell with write permissions… so child processes that use that fd will be able to modify the shell’s memory.
- ASLR isn’t even a problem, we can check the shell’s
mapsfile or any other from the procfs in order to gain information about the address space of the process.
- So we need to
lseek()over the file. From the shell this cannot be done unless using the infamous
In more detail
The steps are relatively easy and do not require any kind of expertise to understand them:
- Parse the binary we want to run and the loader to find out what mappings they need. Then craft a “shell”code that will perform, broadly speaking, the same steps that the kernel does upon each call to
- Create said mappings.
- Read the binaries into them.
- Set up permissions.
- Finally initialize the stack with the arguments for the program and place the auxiliary vector (needed by the loader).
- Jump into the loader and let it do the rest (load libraries needed by the program).
- Obtain from the
syscallfile the address to which the process will return after the syscall it is executing.
- Overwrite that place, which will be executable, with our shellcode (through
memwe can modify unwritable pages).
- Pass the program we want to run to the stdin of the process (will be
read()by said “shell”code).
- At this point it is up to the loader to load the necessary libraries for our program and jump into it.
Oh, and all of this must be done in shell scripting, or what would be the point?
Well, there are a couple of TODOs. Besides this, you may have noticed that I do not know much about shell scripting (I am more of a C programmer) and I am sure I must have won a decade worth of “useless use of an echo” awards and the rest of variants just with a fraction of this project.
- Improve code style and performance.
- Port to other shells.
- Allow run the program with a non-empty environment.
Anyway, all contribution is welcome. Feel free to fork and PR.
Recently I have come to know that Sektor7 had already published this almost-exact same technique on their blog a few years ago.
Despite this, I thought this technique independently in, now almost, its entirety. Probably the smarter piece of this technique is the use of the inherited file descriptor, idea provided by David Buchanan (inspired, I think, by Sektor7’s blog) almost a year before I even started thinking about this topic. This alone not only makes the technique much simpler and neat, it also makes it far deadlier by eliminating the need to disable ASLR. His tweet also made me realize how stupid I was for not noticing that
mem allowed to write to non-writable pages, hence making the ROP unnecessary… This ultimately also has the desired effect of making this significantly easier to port to other ISAs.
Either way, I hope I will be able to spread this technique much further, which is what matters.
I would like to thank Carlos Polop, a great pentester and better friend, for making me think about this subject, and for his helpful feedback and interest, oh and the name of the project. I am sure that if you are reading this you have already used his awesome tool PEASS and found helpful some article in his book HackTricks. I also thank him for helping me with the talk at the RootedCon 2022.
This technique can be prevented in several ways.
- Not installing
dd(maybe even go distroless?).
ddwhere only root can run it.
- Using a kernel compiled without support for the
Questions? Death threats?
Feel free to send me an email to [email protected].