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

API hacking lab setup

 Follow the commands to install and configure API hacking lab: 1. Install kali linux and update all the packages.  apt update -y apt upgrade -y or apt dist-upgrade -y or apt full-upgrade -y If you face any problem regarding update, install cloud flare warp in the host machine, then again start updating packages in your kali vm.  2. Install and configure burpsuite professional.  After that open burpsuite and go to Extensions tab. Click on BAppStore. Search for Autorize extension, It will help us to automate authorization testing. Click on Download Jython from the right side. From Jython website click on Jython standalone JAR and save it. Go to Extensios > Extensions settings >  under Core extension settings find out Python environment on the right pane. Select the jython jar file that you just downloaded. Now again go to BAppStore and re-search for Autorize extension. You will see Install option this time after selecting Autorize extension. Install it. You ...

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

Installing kansa incident response tool

 Kansa is an IR framework. https://github.com/davehull/Kansa For enterprise data collection, you need to do this first from the admin system: Set-NetConnectionProfile -NetworkCategory Private (In private network) Enable-PSRemoting  from powershell on the system where you want to run this tool. This will enable winrm service with port 5985 and 5986. Check: netstat -naob | findstr "5985"   Also allow tcp port 5985 and 5986 for winrm through the network. You can use  GPO. Though winrm is communicating over http and https but authentication will be happened using kerberos in domain environment.  After downloading it  from the github and unzip it, you need to unlock it using powershell. Need powershell v3 or later. ls -r *.ps1 | Unblock-File Powershell policy bypass: Set-ExecutionPolicy AllSigned | RemoteSigned | Unrestricted From FOR508 course: .\kansa.ps1 -OutputPath .\Output\ -TargetList .\hostlist -TargetCount 250 -Verbose -Pushbin -Pushbin is requir...