offensive-windows-mitigations
This skill provides a comprehensive methodology for understanding Windows exploit mitigations including ASLR, DEP/NX, CFG, CET, SEHOP, Heap Guard, and ACG. Use it when researching how these protections work, learning to detect active mitigations on target systems, testing exploits against protected binaries, or preparing to study mitigation bypass techniques in subsequent training modules.
git clone --depth 1 https://github.com/SnailSploit/Claude-Red /tmp/offensive-windows-mitigations && cp -r /tmp/offensive-windows-mitigations/Skills/infrastructure/offensive-windows-mitigations ~/.claude/skills/offensive-windows-mitigationsSKILL.md
# SKILL: Week 6: Understanding Windows Mitigations ## Metadata - **Skill Name**: windows-mitigations - **Folder**: offensive-windows-mitigations - **Source**: https://github.com/SnailSploit/offensive-checklist/blob/main/6-windows-mitigations.md ## Description Deep-dive on Windows exploit mitigations: ASLR, DEP/NX, CFG, CET/Shadow Stack, SEHOP, Heap Guard, ACG, Arbitrary Code Guard. Covers both the protection mechanism and known bypass techniques. Use when researching Windows exploit mitigations, planning bypass strategies, or understanding protection depth. ## Trigger Phrases Use this skill when the conversation involves any of: `Windows mitigations, ASLR, DEP, NX, CFG, CET, shadow stack, SEHOP, heap guard, ACG, mitigation bypass, exploit mitigation, Windows hardening` ## Instructions for Claude When this skill is active: 1. Load and apply the full methodology below as your operational checklist 2. Follow steps in order unless the user specifies otherwise 3. For each technique, consider applicability to the current target/context 4. Track which checklist items have been completed 5. Suggest next steps based on findings --- ## Full Methodology # Week 6: Understanding Windows Mitigations ## Overview _created by AnotherOne from @Pwn3rzs Telegram channel_. Last week you learned basic exploitation in an environment without protections. This week, you'll learn about the defensive mechanisms that modern Windows systems employ to prevent those attacks. Understanding these mitigations is essential before learning to bypass them (Week 8). Week 7 continues with enterprise security topics (offensive reconnaissance, Windows 11 24H2/25H2 mitigations, cross-platform defenses). **This Week's Focus**: - Understand how each mitigation works - Learn to detect active mitigations - Verify mitigation effectiveness - Test exploits against protected binaries - Prepare for Week 7's boundaries and Week 8's bypass techniques ### Prerequisites Before starting this week, ensure you have: - Completed Week 5: Basic Exploitation (Linux) - you should be able to exploit stack overflows, build ROP chains, and use pwntools - A Windows 11 VM (isolated, snapshot before each exercise) - Visual Studio 2022 Build Tools installed - WinDbg Preview installed - Basic familiarity with x64 assembly and calling conventions ### Week 6 Deliverables By the end of this week, you should have completed the following: - [ ] **Lab Environment**: Windows 11 VM with Visual Studio Build Tools, WinDbg Preview, and Sysinternals installed - [ ] **Test Binaries**: Compiled `vulnerable_suite_win_mitigated.c` and `vuln_server_win.c` with various mitigation flags - [ ] **DEP Verified**: Demonstrated DEP blocking shellcode execution with crash analysis (Exception Code 0xC0000005, Param 8) - [ ] **ASLR Measured**: Recorded addresses of `check_aslr.exe` across 3 reboots and documented randomization behavior - [ ] **Stack Cookie Tested**: Triggered `/GS` cookie check failure and analyzed in WinDbg - [ ] **CFG Validated**: Demonstrated CFG blocking indirect call to invalid target - [ ] **Crash Dumps Analyzed**: Created at least 3 crash dumps and identified which mitigation caused each termination using `!analyze -v` - [ ] **Week 5 Exploit Retesting**: Re-ran Week 5 exploits against mitigated binaries and documented failures - [ ] **Mitigation Audit Report**: Generated system-wide and per-binary mitigation audit using PowerShell scripts - [ ] **Hardening Capstone**: Completed the SecureServer v1.0 hardening exercise (Day 7) ### Context Why Mitigations Matter: Modern exploits chain multiple vulnerabilities and bypass layers of protection. Understanding mitigations helps you: - Recognize when an exploit is blocked vs. when it succeeds - Analyze crash dumps to identify exploitation attempts - Design defense-in-depth strategies - Prepare for Weeks 7-8 (advanced mitigations and bypass techniques) **Recent CVEs Demonstrating Mitigation Importance**: | CVE | Vulnerability | Mitigations Involved | Outcome | | -------------- | ------------------------------- | -------------------- | ------------------------------------- | | CVE-2024-21338 | AppLocker (appid.sys) EoP | KASLR, SMEP, kCFG | Admin-to-Kernel bypass of kCFG | | CVE-2024-30088 | Authz Kernel TOCTOU | KASLR, SMEP, CFG | Exploited via race condition | | CVE-2023-36802 | MSKSSRV Object Type Confusion | KASLR, SMEP, CFG | Pool spray + type confusion to EoP | | CVE-2025-29824 | CLFS Driver Use-After-Free | KASLR, SMEP | Zero-day exploited in wild (Apr 2025) | | CVE-2024-49138 | CLFS Heap-Based Buffer Overflow | DEP, ASLR, KASLR | EoP exploited in wild (Dec 2024) | | CVE-2023-32019 | Windows Kernel Info Disclosure | KASLR | Leaked kernel memory bypassing KASLR | | CVE-2023-28252 | CLFS Driver EoP | KASLR, SMEP | Abused CLFS log file parsing | | CVE-2022-34718 | Windows TCP/IP RCE (EvilESP) | DEP, ASLR, CFG | Required sophisticated heap grooming | **Connection to Week 4 (Crash Analysis)**: When you receive a crash dump, the exception codes reveal which mitigation stopped the exploit: ```text Week 4 Crash Analysis -> Week 6 Mitigation Identification ───────────────────────────────────────────────────────── Process Exit Code WinDbg Exception Code Mitigation ────────────────────── ───────────────────── ────────── 0xC0000005 (Param[0]=8) 0xC0000005 DEP violation (execute on NX page) 0xC0000409 0xC0000409 (subcode 2) /GS stack cookie corruption 0x80000003 0xC0000409 (subcode 10) CFG indirect call validation failed 0x80000003 0xC0000407 CET shadow stack mismatch 0xC0000374 0xC0000374 Heap integrity check failed IMPORTANT: Python/cmd see the PROCESS E
Active Directory attack methodology for internal network red team engagements. Covers reconnaissance (BloodHound, PowerView, ADExplorer), credential abuse (Kerberoasting, ASREProasting, NTLM relay, LLMNR/NBT-NS poisoning), privilege escalation (ACL abuse, GPO abuse, unconstrained/constrained delegation), lateral movement (Pass-the-Hash, Pass-the-Ticket, Overpass-the-Hash, WMI/WinRM/PsExec), persistence (Golden/Silver/Diamond Tickets, DCSync, DCShadow, AdminSDHolder, Skeleton Key), forest trust attacks, ADCS abuse (ESC1-ESC15), and modern MDI/Defender for Identity evasion. Use when assessing on-prem AD, hybrid AD/Entra ID environments, or ADCS deployments.
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC discipline including attribution avoidance and indicator management, EDR and AMSI evasion techniques using direct syscalls and unhooking, data collection with chain-of-custody controls, and structured reporting with purple team debrief workflows. Covers assumed-breach, external-to-internal, insider threat, and hybrid physical-cyber engagement scenarios with MITRE ATT&CK mapping throughout. Targets operators planning or executing adversary simulation engagements against mature defenders.
Anti-forensics and evidence destruction techniques for red team operators conducting authorized engagements. Covers log clearing on Windows (wevtutil, Clear-EventLog, ETW provider patching) and Linux (journal truncation, utmp/wtmp binary editing, syslog manipulation), timestamp manipulation via Timestomp and SetMACE to defeat timeline analysis, filesystem-level anti-forensics including NTFS Alternate Data Streams for payload hiding and secure deletion with sdelete/shred, memory artifact removal to counter live forensics, disk artifact manipulation targeting MFT entries and USN journal records, network forensics evasion through encrypted C2 channels and DNS-over-HTTPS tunneling, and anti-VM/sandbox detection to avoid dynamic analysis environments. Tools: Timestomp, wevtutil, sdelete, shred, MimiPenguin, Invoke-Phant0m. Aligns to MITRE ATT&CK T1070 (Indicator Removal), T1027 (Obfuscated Files or Information), T1497 (Virtualization/Sandbox Evasion). Each technique includes the forensic artifact it targets, the destruction or manipulation method, and the defender perspective so operators understand detection gaps they must account for.
Advanced API exploitation methodology focused on business logic abuse and sophisticated attack patterns that bypass traditional security controls. Covers business logic bypass through API call chaining and workflow manipulation. Addresses GraphQL-specific attacks including batching for credential brute-force, query depth exploitation, and introspection abuse. Includes pagination exploitation for data exfiltration, webhook hijacking for SSRF and data interception, and resource exhaustion through algorithmic complexity attacks. Covers race conditions in API transactions using parallel request techniques. Provides comprehensive JWT manipulation including algorithm confusion, kid injection, jku/x5u abuse, and claim tampering. Details API key leakage detection across source repositories, client-side code, and error messages. Covers undocumented endpoint discovery through predictable naming, debug routes, and source map analysis. Tooling includes Arjun, ParamSpider, jwt_tool, and GraphQL Voyager. Designed for authorized penetration testers targeting business logic layers that automated scanners miss.
Comprehensive API security testing methodology covering REST, gRPC, and WebSocket attack surfaces. Addresses the full OWASP API Security Top 10 2023 including BOLA/IDOR, broken authentication, excessive data exposure, rate limiting bypass, BFLA, mass assignment, SSRF, and security misconfiguration. Includes REST-specific attacks such as HTTP verb tampering, content-type switching, and parameter pollution. Covers gRPC exploitation through protobuf interception, reflection API enumeration, and metadata injection. Addresses WebSocket vulnerabilities including origin bypass, message injection, and cross-site WebSocket hijacking. Provides tooling guidance for Burp Suite, Postman, grpcurl, websocat, and mitmproxy. Each technique includes detection signatures and defensive indicators so you understand what artifacts your testing leaves behind. Designed for authorized penetration testing engagements against API-driven architectures.
Bluetooth Low Energy (BLE) attack methodology — GATT enumeration, characteristic read/write without auth, pairing downgrade (Just Works forced), LE Secure Connections bypass, MITM via active relay, sniffing with Sniffle (TI CC1352) / Ubertooth / Frontline, encryption key extraction (LE Legacy Pairing crackable, LE Secure Connections strong), proximity authentication abuse (cars, locks), and companion-app trust analysis. Use for IoT BLE devices, smart locks, fitness trackers, medical devices, BLE beacons, or any device pairing over BLE.