Shell-History - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/shell-history/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 03 Jan 2024 14:30:00 +0000Linux Shell History Clearing via Environment Variableshttps://feed.craftedsignal.io/briefs/2024-01-linux-shell-history-clearing/Wed, 03 Jan 2024 14:30:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-linux-shell-history-clearing/Attackers may clear shell history on Linux systems to evade detection by manipulating environment variables related to shell history, such as HISTSIZE and HISTFILE, to prevent command logging.Attackers on Linux systems may attempt to clear shell history to hide their activities and evade detection. This is achieved by manipulating environment variables that control the shell's history logging behavior. By setting variables like HISTSIZE or HISTFILESIZE to 0, HISTCONTROL to ignorespace, or redirecting HISTFILE to /dev/null, attackers can effectively disable or erase the command history, making it difficult for defenders to track their actions. This technique is often employed after gaining initial access to a system to mask subsequent malicious activities, such as privilege escalation, lateral movement, or data exfiltration. This activity can occur on any compromised Linux host, regardless of the specific distribution or kernel version. Detecting this behavior is crucial for identifying potentially compromised systems and uncovering attacker activity.

Attack Chain

  1. Attacker gains initial access to a Linux system, potentially through SSH or other remote access methods.
  2. Attacker identifies the current shell and its configuration.
  3. Attacker sets HISTSIZE or HISTFILESIZE environment variables to 0 to prevent new history entries from being saved.
  4. Attacker sets HISTCONTROL to ignorespace to prevent commands starting with a space from being saved.
  5. Attacker redirects the HISTFILE environment variable to /dev/null to discard the history file.
  6. Attacker executes commands related to enumeration, privilege escalation, or lateral movement.
  7. The executed commands are not recorded in the shell history due to the manipulated environment variables.
  8. Attacker attempts to remove traces of their presence and maintain stealth by avoiding logging their activities.

Impact

Successful clearing of shell history hinders forensic investigations and incident response efforts. By removing command history, attackers make it difficult to reconstruct their actions on the compromised system. This can lead to delayed detection, prolonged dwell time, and increased damage. The number of victims can vary depending on the scope of the attack, but any Linux system where an attacker gains shell access and clears the history is potentially affected. Sectors targeted may include any organization relying on Linux servers for critical infrastructure or data storage.

Recommendation

  • Enable Elastic Defend and configure the linux.advanced.capture_env_vars setting to capture HISTSIZE, HISTFILESIZE, HISTCONTROL, and HISTFILE to enable the detection rule to function properly.
  • Deploy the Sigma rule "Linux Shell History Clearing via Environment Variables" to your SIEM to detect this behavior, and tune it according to your environment.
  • Investigate any alerts generated by the detection rule "Linux Shell History Clearing via Environment Variables" to determine the scope and impact of the potential compromise.
  • Monitor for suspicious processes that modify shell environment variables related to history, using the provided Sigma rules as a starting point.
]]>highadvisorydefense-evasionlinuxshell-history