Skip to main content

Detecting privilege escalation, incident response and mitigation, Splunk

 For example, your sensitive file is configured in such a way to splunk so that any change's on that file would let you know. 

You now know your /etc/passwd file has been changed and the user did this her/her uid is 1002 and the user user /bin/cp exe tool to do this. 

From the victim server, auditd and sshd logs are forwarded to splunk. Our task is find out the user's name. 

Query in splunk:

source="/var/log/victim-server/audit.log" uid=1002 /Home

Now we shall know the username of uid 1002 which is victor.

Now this user victor may try to ssh on the victim-server. We want to know the ip address of the system from where victor trying for ssh. 

source="/var/log/victim-server/sshd.log" "failed password for victor"

now we shall get the ip address of victor's machine. 

Now there is another way to get the username of uid 1002, for that you need to what does acct auid field means in auditd logs. acct for accounts and auid for audit uid. 

source="/var/log/victim-server/audit.log" auid=1002 AND acct=* AND exe="*sshd" | top 0 acct

or 

source="/var/log/victim-server/audit.log" auid=1002 AND acct=* AND | top acct


Now investigating the audit logs, how to find what tool attacker download over https after getting access on the system?

source="/var/log/victim-server/audit.log" https   (we could also use .com keyword)

 

Now say attacker switch the user account using su command. How you gonna find that?

source="/var/log/victim-server/audit.log" uid="1002" exe="/bin/su" | top 0 acct

or

source="/var/log/victim-server/audit.log" uid="1002" exe="/bin/su"

Now we shall get the name of user account that had been switched to. 


Now access the server to investigate further:

after accessing the server issue sudo -i command to get root access. 

now type history command or cat /root/.bash_history command to see what commands previously launched by the attacker. 

check /root/.ssh/authorized_keys files. 

In this case the vulnerability lies in /bin/cp utility. Because SUID permission is set on /bin/cp utility. When this permission is set then command execute in root privileges and any unprivileged user can write to any file on the system if they use cp tool. 

so to find that tool, 

find / -perm -u=s -type f 2>/dev/null

after find that tool, now issue the below command. 

chmod u-s /bin/cp


Now remove scanner user from the /etc/passwd file. You can use vim or nano or mousepad or pluma tool to do that or can use the below command. 

sed -i "$ d" /etc/passwd

Also remove the entry from /root/.ssh/authorized_keys file. 

sed -i "$ d" /root/.ssh/authorized_keys

Avi



Comments

Post a Comment

Popular posts from this blog

Install Nessus from docker

Docker installation. Give the below commands one by one. apt install docker-cli or apt install docker.io After the installation is complete, if you are inside wsl then give this command to start docker, because inside wsl systemd (systemctl) does not work: service docker start WSL troubleshooting : If the above command " service docker start " does not work then use below command: dockerd (It may not work if any previous docker process is running. It will show you pid of that process. Use this command to kill that process " kill -9 pid " and run dockerd command again) If " docker ps -a " giving error like " Cannot connect to the Docker daemon at unix:///run/podman/podman.sock. Is the docker daemon running? " This is because you may installed podman-docker package. If you remove the package still you will get this error but you should remove the package. Then issue this command: env | grep -i docker DOCKER_HOST=unix:///run/podman/podman.sock   --...
Post a Comment
Read more

Installtion of SQLMutant tool

This tool is perfectly works on ubuntu 24 system. And I found it is not working properly in kali linux 24 version.   https://github.com/blackhatethicalhacking/SQLMutant/tree/main This tool need to use along with sqlmap tool. Showing this cheat sheet for kali or debian based system.  This tool actually analyze everything and give you the vulnerable url where sql injection is possible. You just need to use then sqlmap to exploit that.   Prerequisite: apt install pipx -y (for ubuntu) pip3 install uro or pipx install uro pipx ensurepath pipx completions  (not needed)  source ~/.bashrc   or restart system If go tool is not installed then run the below two commands first ( golang-go ) or follow this link to install go (https://mahimfiroj.blogspot.com/2024/12/installing-nuclei-in-kali.html) otherwise skip this step.   dpkg -l | grep packagename (Using this command you can check package is installed or not) apt install gccgo-go -y or apt install gol...
Post a Comment
Read more

Installing nuclei and go tool in kali

 First you need to install go: https://go.dev/doc/install You need to download this go tool go1.23.4.linux-amd64.tar.gz by clicking the Download button.  Say you are root and download the tool in your Downloads directory. Now run the below command: tar -C /usr/local -xzf go1.23.4.linux-amd64.tar.gz (if this cmd fails then you need to move this tool to /usr/local folder then run this cmd tar -xzf  go1.23.4.linux-amd64.tar.gz) Now add /usr/local/go/bin to the PATH environment variable. You can do this by adding the following line to your $HOME/.profile or /etc/profile (for a system-wide installation): export PATH=$PATH:/usr/local/go/bin Now use the following command for immediate effect. Preventing you from log off then log back in: source $HOME/.profile go version (to check it is installed successfully) Install nuclei: go install -v github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest or apt install nuclei nuclei -update-templates nuclei -u https://www.domain....
Post a Comment
Read more