Adversaries may hijack a legitimate user's SSH session to move laterally within an environment. Secure Shell (SSH) is a standard means of remote access on Linux and macOS systems. It allows a user to connect to another system via an encrypted tunnel, commonly authenticating through a password, certificate or the use of an asymmetric encryption key pair.

In order to move laterally from a compromised host, adversaries may take advantage of trust relationships established with other systems via public key authentication in active SSH sessions by hijacking an existing connection to another system. This may occur through compromising the SSH agent itself or by having access to the agent's socket. If an adversary is able to obtain root access, then hijacking SSH sessions is likely trivial.[1],[2],[3],[4]

SSH Hijacking differs from use of SSH because it hijacks an existing SSH session rather than creating a new session using Valid Accounts.

References

  1. Duarte, H., Morrison, B. (2012). (Mis)trusting and (ab)using ssh. Retrieved January 8, 2018.
  2. Adam Boileau. (2005, August 5). Trust Transience: Post Intrusion SSH Hijacking. Retrieved December 19, 2017.
  3. Beuchler, B. (2012, September 28). SSH Agent Hijacking. Retrieved November 17, 2024.
  4. Hodgson, M. (2019, May 8). Post-mortem and remediations for Apr 11 security incident. Retrieved November 17, 2024.

Kapcsolt feladatok

Kapcsolatok
Kapcsolattípus Feladat
is related to Techniques
is blocked by Restrict File and Directory Permissions
is blocked by Disable or Remove Feature or Program
is blocked by Password Policies
is blocked by Detection Strategy for SSH Session Hijacking
is blocked by Privileged Account Management
is blocked by Asset Governance
is blocked by Prohibition Of Changes
is blocked by Statutory, Regulatory & Contractual Compliance
is blocked by Configuration Management Program
is blocked by Least Functionality
is blocked by Continuous Monitoring Policy
is blocked by Database Encryption
is blocked by Personnel Transfer
is blocked by Identity & Access Management (IAM)
is blocked by Privileged Account Management (PAM)
is blocked by Password-Based Authentication
is blocked by Authenticator Feedback
is blocked by Restrictions on Shared Groups / Accounts
is blocked by Network Device Plane Segmentation
is blocked by Zero Trust Architecture (ZTA)
is blocked by Vulnerability Remediation Process
is blocked by Asset Inventories
is blocked by Access Restriction For Change
is blocked by Executive Leadership Oversight of Security, Compliance & Resilience Controls
is blocked by Secure Baseline Configurations
is blocked by Continuous Monitoring
is blocked by Public Key Infrastructure (PKI)
is blocked by Separation of Duties (SoD)
is blocked by Account Management
is blocked by Authenticator Management
is blocked by Access Enforcement
is blocked by Least Privilege
is blocked by Identification & Authentication for Organizational Users
is blocked by Remote Access
is blocked by Session Integrity
is blocked by Vulnerability Scanning