How to Validate Exploitability Without Running a Live Exploit

Summary
In a sponsored article, Picus advocates testing exploitability by emulating attacker behaviors against deployed controls. A Nightmare-Eclipse example shows how defenders could test privilege escalation, credential access and Defender tampering without running the real 😅
Key points
- The article argues that rising CVE volume and shorter time-to-exploit make patching alone insufficient for prioritizing risk.
- It proposes mapping an exploit to required attacker behaviors and testing whether deployed controls block each step, instead of firing a live exploit.
- The article describes BlueHammer as using a Windows Defender remediation workflow and a race condition to access registry hives through a Volume Shadow Copy and escalate privileges.
- It says RedSun repurposes a related primitive to overwrite a system executable, while UnDefend disrupts Defender signatures and can misreport its status.
- Picus says its emulation can test service creation, Volume Shadow Copy hive access and Defender service disruption without running the described malware.
- The article recommends combining safe behavior emulation with live exploitation where safe, and repeating validation as environments change.
Article Details
- Defense Focus
- Validate whether vulnerability exploit chains can succeed against deployed controls without launching live exploits, and prioritize patching and hardening based on observed defensive gaps.
- Detection Methods
- Monitor for creation of temporary Windows services that could be used to execute a payload as SYSTEM.
- Detect access to the SAM, SYSTEM, and SECURITY registry hives through Volume Shadow Copy, including activity consistent with offline NTLM hash extraction.
- Test Defender tamper protection against attempts to stop its service, block signature updates, or prevent signature reloads.
- Check for discrepancies between Defender's reported health and the actual state of its service and signature files.
- Data Sources
- Windows service creation events
- Volume Shadow Copy access to the SAM, SYSTEM, and SECURITY hives
- Windows Defender service status and signature-file state
- Defender signature update and reload activity
- EDR console health status
- Platforms
- Windows systems
- EDR consoles
- Defensive Actions
- Map each vulnerability to the attacker behaviors required to exploit it, then test those behaviors against deployed controls without firing the exploit.
- Run the behavior tests in sequence to determine whether the full chain can complete on an asset.
- Prioritize patching and hardening where the tested chain would succeed.
- Use live exploit testing only where it is safe; use behavior-chain validation for restricted, air-gapped, business-critical, or newly disclosed cases.
- Repeat validation after environment or configuration changes and re-check earlier verdicts.
MITRE ATT&CK
T1003.002 · Security Account ManagerBlueHammer reads the SAM hive from a Volume Shadow Copy and extracts local NTLM hashes.T1068 · Exploitation for Privilege EscalationBlueHammer exploits a Windows Defender race condition to read privileged files and escalate local privileges to SYSTEM.T1543.003 · Windows ServiceBlueHammer's final execution step registers a temporary Windows service so its payload runs as SYSTEM; the article also describes safely emulating service creation.T1562.001 · Disable or Modify ToolsUnDefend blocks Windows Defender signature updates and reloads, and the described chain also includes stopping the Defender service.
