Skip to main content

capture credentials from bash history | .bash_history | ~/.bash_history | clear history or clear bash history in linux

https://attack.mitre.org/techniques/T1552/003/

 

attacker may search bash command history on compromised systems because sometimes users tend to pass username and password over command line to the program. 

when user logs out then all the commands are flushed out to .bash_history file. for each user the file resides in the same location. ~/.bash_history 

attacker can abuse this by looking through the file for potential credentials. 

 

Mitigation:

there are multiple methods of preventing a users command history from being flushed to their .bash_history file, including use of the following commands:

off logging:

set +o history

and set -o history to start logging again. 

 

another way:

clean command history:

history -c

to make sure changes are written to disk, use:

history -w 

to make more sure the history is cleared when existing a session, the following command comes in handy:

cat /dev/null > ~/.bash_history && history -c && exit

 

 

 

 

 

permanently disable bash history:

echo 'set +o history' >> ~/.bashrc

next time when user login to the shell it will not store any commands to a history file .bash_history

to apply this settings immediately for the current shell session execute the .bashrc file:

. ~/.bashrc

 

disable a command history system wide:

echo 'set +o history' >> /etc/profile

it will be effective for the new users created after this.

 

 

if you dont have write permission on .bash_profile file then run the below command:

commands are written to the HISTFILE environment variable, which is usually .bash_history. we can echo it to see the location:

echo $HISTFILE

/root/.bash_history (this is the location)

we can use the unset command to remove the variable:

unset HISTFILE

now if we echo it then nothing will shows up. 

 

we can also make sure the command history is not stored by sending it to /dev/null

or export HISTFILE=/dev/null 

or HISTFILE=/dev/null

and now history will now be sent to /dev/null

echo $HISTFILE

/dev/null

then all commands afterwards wont be logged within that session. 

or if you have write permission, and want this behavior in each login then:

echo 'unset HISTFILE' >> ~/.bash_profile

echo 'unset HISTFILE' >> ~/.bashrc

 

ln -s /dev/null ~/.bash_history

 

 

 

Comments

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   --...

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...

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....