MGM Cyber Attack Deep-Dive - Attacker's Perspective
- Infiltration and Privilege Escalation: The Alpha / BlackCat group infiltrated MGM's network, targeting their Okta Agent servers to obtain uncrackable passwords from domain controller hash dumps. They secured super administrator privileges to MGM's Okta and global administrator privileges to their Azure tenant, establishing a strong foothold in the network.
- MGM's Response and Lockout: Upon discovering the breach, MGM hastily shut down their Okta Sync servers, inadvertently locking themselves out of their Okta environment. Their attempt to evict the attackers faltered due to weak incident response playbooks and inadequate administrative capabilities, compounded by a lack of understanding of network functionalities among their network engineers.
- Ransomware Attack and Negotiation: Following a failed negotiation attempt, the group escalated their attack, deploying ransomware on over 100 ESXi hypervisors within MGM's environment. MGM sought external assistance to contain the escalating situation.
- Communication and Data Exfiltration: The attackers established a secure communication channel with MGM, offering a download link for all exfiltrated data protected by a password derived from two senior executives' passwords. The situation was further complicated by uncertainty over the identity of the MGM representative in the communication channel.
Critical Kubernetes Vulnerabilities Pose High Risk to Windows Nodes
- CVE-2023-3676 and Related Flaws: Three interrelated high-severity vulnerabilities have been identified in Kubernetes, affecting all environments with Windows nodes. The central issue, tracked as CVE-2023-3676, allows attackers with low privileges to execute remote code with system privileges on Windows endpoints within a Kubernetes cluster through the application of a malicious YAML file.
- Exploitation and Impact: The vulnerabilities can be exploited by attackers with access to apply privileges in the Kubernetes API, enabling them to inject arbitrary code that will be executed on remote Windows machines with system privileges. The exploitation involves the use of specially crafted path strings parsed as parameters to PowerShell commands, leading to command execution and potentially granting administrator access on the node.
- Affected Versions and Mitigation: Kubernetes environments with Windows nodes running kubelet versions earlier than v1.28.1, v1.27.5, v1.26.8, v1.25.13, and v1.24.17 are affected. It is imperative to update to the fixed versions to mitigate the risk. The Kubernetes community has released patches to address these vulnerabilities, and platforms like AWS, Google Cloud, and Microsoft Azure have issued advisories.
- Root Cause and Prevention: The vulnerabilities stem from insufficient input sanitization in the Windows-specific porting of the kubelet, particularly in handling pod definitions. Moving forward, it is crucial to enhance input validation and sanitization processes to prevent such security lapses, and organizations should monitor Kubernetes audit logs for signs of exploitation, such as pod create events with embedded PowerShell commands.