It has been a tough few weeks for many enterprise security teams fighting a series of severe bugs in Microsoft Windows 10. Shortly after being ‘all hands on deck’ dealing with the remote code execution (RCE) vulnerability dubbed PrintNightmare, IT admins and security teams were plunged into another unexpected crisis thanks to the emergence of the unrelated but familiar sounding ‘HiveNightmare’ bug, aka SeriousSAM.
More formerly tracked as CVE-2021-36934, HiveNightmare is a local privilege escalation (LPE) that allows any standard user to achieve SYSTEM privileges, with all the security headaches that that entails: the ability to install malware, delete data, create new user accounts and pretty much conduct any other malicious behavior so desired.
Although HiveNightmare requires an attacker to have gained a foothold on a target system, what makes CVE-2021-36934 of particular concern is that having done so, this bug is trivial to exploit. An attacker that either accesses the target locally or remotely (such as via SSH) can very quickly and easily take advantage of a vulnerable system. Consequently, it is imperative that admins and security teams understand the details of the HiveNightmare vulnerability, how it can be exploited, and how it can be mitigated.
What Is The HiveNightmare Vulnerability?
“HiveNightmare” is an NTFS-centric, access control list (ACL) flaw which affects Windows 10 builds 1809 up to and including 21H1. Upon exploitation, non-privileged users may potentially gain access to execute arbitrary code or read sensitive data. Specifically, attackers may leverage this vulnerability to extract registry hive data, including hashed passwords, which can in turn be used to further elevate privilege.
Attempts to attack hive data files have typically required the attacker to target the registry databases in an inactive or ‘offline’ Windows session. HiveNightmare greatly simplifies the attack, allowing (amongst other things) for the extraction of sensitive registry data from Volume Shadow Copies. Attackers can potentially execute arbitrary code with SYSTEM privileges, allowing for full control.
The heart of the problem lies in any user’s ability to read files in the
C:\WINDOWS\SYSTEM32\CONFIG folder. This folder includes the private system-wide Windows registry files, as well as the frequently-targeted SAM (System Account Manager) file, which contains all the local user NTLM password hashes.
When the following command is run, vulnerable systems will show
BUILTIN\Users group having
RX (Read + Execute) permissions on the
> icacls C:\Windows\System32\config\SAM
Attackers can leverage this insecure ACL permission to elevate privileges to local admin/SYSTEM. In organizations managed by image templates containing local users, this can be exploited for automatic lateral movement or to kickstart a worm infection mechanism.
How Is HiveNightmare Used In Attacks?
At the time of writing, the majority of activity around HiveNightmare is academic or ‘proof-of-concept’ in nature. Having said that, we have observed some examples of malware based on (or around) the code snippets that have cropped up. Dozens of such examples have already been submitted to VirusTotal in recent days.
Even though exploitation is trivial, multiple exploits have been published in a variety of source code languages:
As noted above, it is in general not possible to access hive data files when the system is ‘live’ as these files are locked when in use. However, since Windows 10 keeps system restore points (aka Volume Shadow Copies) that contain copies of the hive data files, an attacker can extract copies of these files from any existing snapshots.
> vssadmin list shadows
lists saved snapshots for the device.
The built-in CERTUTIL command can then be used to dump the SAM database to the TEMP folder.
It is important to note that while the concept of exfiltrating credentials via stolen SAM data is not novel, HiveNightmare goes a long way towards simplifying the process for attackers. This observation is further solidified by the uptick in submissions to public malware repositories of ‘commodity’ malware attempting to incorporate this exploit.
General Mitigations and Workarounds
The HiveNightmare vulnerability was disclosed in mid-July 2021 and officially addressed by Microsoft on July 20, 2021. This first disclosure from Microsoft included possible workaround and manual mitigation steps.
- Delete any Restore Points and VSS Volumes
- Restrict user access to
icacls %windir%\system32\config\*.* /inheritance:e
Monitoring & Threat Hunting:
- Any access to a path containing regex:
- Suspicious creation of symbolic links containing
HarddiskVolumeShadowCopy, cmdline regex:
(as well as other variants such as PowerShell, fsutil.exe etc.)
It has also been noted that enabling periodic backup of the system registry to the “RegBack” folder will restore the ACL permissions to the more secure setting after a reboot. This was, in fact, Windows 10 default behavior until version 1803. As stated by Microsoft at the time, this change was intended to help reduce the overall disk footprint size and users were recommended to recover corrupt registry hives via a system restore point. In hindsight, that recommendation looks less than wise, and it will be interesting to see if Microsoft revises that advice.
Current guidance by Microsoft is available here.
Mitigating HiveNightmare With SentinelOne
The SentinelOne Singularity Platform detects and prevents attacks associated with CVE-2021-36934 (HiveNightmare) with the current Endpoint Security Agent release (starting 4.1). The Agent’s Intrusion Detection engine autonomously blocks attempts to access sensitive SAM information from a volume shadow copy.
To enable the protection, please follow the steps mentioned in this KB support article.
HiveNightmare is certainly poised to become a standard weapon in the modern attacker’s armory. Escalating privileges and stealing credentials are tactics every threat actor desires to accomplish, and HiveNightmare just made these a whole lot easier to achieve. Organizations that fail to take the appropriate proactive mitigation steps are putting a target on their backs that may cost them dearly in the future. IT and security teams are, therefore, strongly advised to follow the mitigation procedures described above. If you need further assistance or would like to know more about how SentinelOne can help secure your organization, contact us or request a free demo.
Credential Dumping: Security Account Manager – T1003.002
Unsecured Credentials: Credentials In Files – T1552.001
Data Encoding: Standard Encoding – T1132.001
Credential Dumping: NTDS – T1003.003
Signed Binary Proxy Execution- T1218
Indirect Command Execution – T1202
Obfuscated Files or Information – T1027
Deobfuscate/Decode Files or Information – T1140
Query Registry – T1012
Read more about Cyber Security
- MeteorExpress | Mysterious Wiper Paralyzes Iranian Trains with Epic Troll
- The Rise of Big Data | Solving Today’s Challenges with SentinelOne XDR (Part 1)
- Detecting XLoader | A macOS ‘Malware-as-a-Service’ Info Stealer and Keylogger
- PrintNightmare | Latest Patch Almost Puts Microsoft Vulnerability to Bed
- CVE-2021-3122 | How We Caught a Threat Actor Exploiting NCR POS Zero Day
- Conti Unpacked | Understanding Ransomware Development As a Response to Detection
- Cyber Insurance: Navigating A Tough New World In the Age of Ransomware
- REvil’s Grand Coup | Abusing Kaseya Managed Services Software for Massive Profits
- Kubernetes Security: Challenges, Risks, and Attack Vectors