Exploit Databases and Resources
Overview
Finding public exploits is one of the most time-critical skills on the OSCP exam. When you’ve identified a vulnerable service during enumeration, the clock is ticking — you need to locate a working exploit, verify it matches your target, and adapt it if necessary. This chapter provides an exhaustive reference to every major exploit database and resource you’ll need, with practical strategies for each.
The key mindset: no single resource is sufficient. A successful pentester cross-references multiple databases, uses each for its strengths, and maintains a disciplined workflow for evaluating exploit quality.
1. Exploit-DB (Offensive Security)
1.1 Overview
Exploit-DB is the single most important resource for OSCP candidates. Owned and operated by Offensive Security — the same organization that creates the OSCP exam — it is the authoritative repository for publicly disclosed exploits, shellcode, and security research papers.
| Attribute | Detail |
|---|---|
| URL | https://www.exploit-db.com |
| Owner | Offensive Security |
| Content | Exploits, shellcode, security papers, and tools |
| Update Frequency | Daily (new submissions reviewed and published) |
| Database Size | 55,000+ exploits, 2,000+ papers, 1,500+ shells |
| License | Public domain (most entries) |
| OSCP Relevance | Critical — this is your #1 resource during the exam |
1.2 Access Methods
Exploit-DB offers four distinct access methods, each with different strengths:
Method 1: Web Interface
The browser-based interface at https://www.exploit-db.com provides:
- Full-text search across all exploit titles, descriptions, and metadata
- Category browsing (Windows, Linux, macOS, iOS, Android, Hardware, Multiple, WebApps)
- Advanced filters: platform, type (remote/local), date range, author
- Comments section on each exploit — community members share success/failure experiences
- Copy-to-clipboard button for quick code extraction
- Download as raw file
Web search tips:
- Use the search bar at the top for quick lookups
- Click “Advanced Search” for filtered queries
- Sort results by “Date Added” (newest first) or “Relevance”
- The URL pattern
https://www.exploit-db.com/exploits/XXXXX/directly links to a specific exploit by EDB-ID
Method 2: Searchsploit (Command-Line Tool)
searchsploit is the CLI companion to Exploit-DB, pre-installed on Kali Linux. It maintains a local mirror of the entire Exploit-DB database, enabling fast offline searches.
Installation and maintenance:
# Verify installation (pre-installed on Kali)
searchsploit --version
# Update the local database (do this before every exam attempt)
searchsploit --update
# Check the local database path
searchsploit --path
# Typical output: /usr/share/exploitdb/
Complete command reference:
# === Basic Searches ===
searchsploit Apache # Search by keyword
searchsploit Apache 2.4 # Multi-word search (AND logic)
searchsploit "CVE-2021-41773" # Search by CVE ID
# === Wildcard Search ===
searchsploit -w "apache" "traversal" # Wildcard: each term searched independently
searchsploit -w "windows" "smb" # Find Windows SMB exploits
# === Platform Filter ===
searchsploit -p windows apache # Only Windows exploits
searchsploit -p linux privilege # Only Linux exploits
searchsploit -p macosx # macOS exploits
searchsploit -p android # Android exploits
searchsploit -p webapps joomla # Web application exploits
# === Type Filter ===
searchsploit -t "remote" apache # Remote exploits only
searchsploit -t "local" windows # Local exploits only (privilege escalation)
searchsploit -t "dos" # Denial of service exploits
# === Mirror to Current Directory ===
searchsploit -m 50383.py # Copy single exploit to current directory
searchsploit -mm Apache 2.4 # Copy ALL matching exploits
# === Open in Editor ===
searchsploit -x 50383.py # Open exploit in default editor (vim/nano)
# === JSON Output (for scripting) ===
searchsploit -j Apache # Output results as JSON
# === Combined Flags ===
searchsploit -p windows -t local -m privilege escalation
# Mirror all Windows local privilege escalation exploits
Searchsploit output format explained:
Apache 2.4.49 - Remote Code Execution (RCE) via Path Traversal | linux/remote/50383.py
--------------------------------------------------------------------------------
Apache 2.4.50 - Path Traversal (Authenticated) | linux/remote/51278.py
Apache 2.4.49 - Denial of Service | linux/dos/50384.sh
Each line shows: Title | Path (platform/category/EDB-ID.extension)
The path tells you:
linux= target platformremote= exploit type50383.py= EDB-ID and file extension (language)
Method 3: Git Repository
Clone the entire Exploit-DB database for offline access or custom tooling:
# Clone the official repository
git clone https://gitlab.com/exploit-database/exploitdb.git
# Directory structure after clone:
exploitdb/
├── exploits/
│ ├── windows/
│ │ ├── local/ # Windows local exploits (privilege escalation)
│ │ ├── remote/ # Windows remote exploits
│ │ └── dos/ # Windows denial of service
│ ├── unix/
│ │ ├── local/
│ │ ├── remote/
│ │ └── dos/
│ ├── linux/
│ │ ├── local/
│ │ ├── remote/
│ │ └── dos/
│ ├── macosx/
│ ├── ios/
│ ├── android/
│ ├── hardware/
│ ├── multiple/ # Cross-platform exploits
│ └── webapps/ # Web application exploits
├── shells/ # Reverse shells, bind shells, encoders
├── papers/ # Security research papers
└── searchsploit # The searchsploit CLI tool
When to use Git clone:
- Building custom exploit search tools
- Working in air-gapped environments
- Integrating exploit data into automated workflows
- Exam preparation (have the database available offline)
Method 4: API Access
Exploit-DB provides a REST API for programmatic access:
# Search via API
curl "https://www.exploit-db.com/search?action=search&filter=apache+2.4"
# Get specific exploit by EDB-ID
curl "https://www.exploit-db.com/exploits/50383/"
# Note: The API returns HTML pages, not JSON.
# For structured data, use the Git repository or searchsploit -j
1.3 Real-World Search Examples
Scenario 1: You find Apache 2.4.51 on a Linux target
# Step 1: Exact version search
searchsploit Apache 2.4.51
# Step 2: If no exact match, broaden to version family
searchsploit Apache 2.4
# Step 3: Search by vulnerability type
searchsploit -w "apache" "path traversal"
# Step 4: Mirror the most relevant exploit
searchsploit -m 50383.py
# Step 5: Read and understand the exploit
cat 50383.py
Scenario 2: Windows local privilege escalation
# Step 1: Identify the OS version
# (from your enumeration: Windows Server 2019)
# Step 2: Search for Windows local exploits
searchsploit -p windows -t local
# Step 3: Narrow by specific vulnerability
searchsploit -p windows -t local "printnightmare"
searchsploit -p windows -t local "CVE-2021-34527"
# Step 4: Mirror promising exploits
searchsploit -mm windows local privilege
Scenario 3: Web application exploitation
# Search webapps category
searchsploit -p webapps
# Search specific application
searchsploit -p webapps "joomla" "3.9"
# Search by vulnerability type
searchsploit -p webapps "sql injection" "drupal"
1.4 Quality Assessment Criteria
Not all Exploit-DB entries are equal. Use this checklist to evaluate exploit reliability:
| Criterion | High Quality Signal | Low Quality Signal |
|---|---|---|
| EDB-ID age | Published 1-6 months ago (tested by community) | Published today (untested) or >2 years old (may be outdated) |
| Author | Known security researcher (e.g., “z3r0d4y”, “d0nut”) | Anonymous, single-letter username, or first-time poster |
| Comments | Multiple comments confirming success | No comments or comments reporting failures |
| Tested On | Specific OS + version listed in header | Generic or missing “Tested On” field |
| Code structure | Clean, commented, error handling present | Minimal comments, no error handling, obfuscated |
| Dependencies | Clear requirements listed | Unclear or missing dependency information |
| File type | .py (Python) or .rb (Ruby) — easy to read/modify |
.c requiring compilation, or binary-only |
| CVE reference | CVE ID referenced in header | No CVE reference |
The “Golden Rule” of Exploit-DB:
If an exploit has been on Exploit-DB for 2-8 weeks and has positive community comments, it has a high probability of working. Brand-new exploits (<48 hours) may be untested. Very old exploits (>1 year) may not work against patched systems.
2. CVE Details
2.1 Overview
CVE Details (https://www.cvedetails.com) is a comprehensive vulnerability intelligence platform that aggregates CVE data with enhanced searchability, vendor/product filtering, and statistical analysis.
| Attribute | Detail |
|---|---|
| URL | https://www.cvedetails.com |
| Content | CVE database with vendor/product/version filtering |
| Key Strength | Granular filtering by vendor, product, and version |
| OSCP Relevance | High — excellent for initial vulnerability research |
2.2 Effective Search Strategy
Step-by-step workflow:
- Navigate to https://www.cvedetails.com
- Select Vendor from the dropdown (e.g., “Apache”, “Microsoft”, “Oracle”)
- Select Product from the secondary dropdown (e.g., “HTTP Server”, “Windows”)
- Select Version — choose the exact version or version range
- Apply filters:
- Severity: CVSS score range (prioritize 7.0+)
- Date range: Filter by publication date
- Has exploit: Show only CVEs with known exploits
- Click on individual CVEs for detailed information
2.3 Advanced Features
Vendor/Product Filtering
The vendor/product/version hierarchy is CVE Details’ killer feature:
Vendor: Microsoft
└── Product: Windows
└── Version: 10, Server 2019, Server 2016, etc.
└── CVEs listed with CVSS scores, dates, and exploit availability
This is invaluable when you’ve identified a specific product version during enumeration. Instead of searching keywords, you navigate directly to the exact vendor → product → version path.
Version Filtering
CVE Details allows you to:
- Select a specific version (e.g., “2.4.49”)
- Select a version range (e.g., “2.4.40 to 2.4.50”)
- View which versions are affected for each CVE
This precision eliminates the guesswork of whether a CVE applies to your target.
Severity Filtering
Filter by CVSS score ranges:
- Critical (9.0-10.0): Prioritize these first
- High (7.0-8.9): Strong candidates
- Medium (4.0-6.9): Consider if no higher-severity options
- Low (0.1-3.9): Usually not worth the effort on exam
Timeline View
The timeline feature shows vulnerability disclosure history for a product over time. This helps you:
- Identify patterns in vulnerability disclosure
- Understand which versions had the most vulnerabilities
- Spot recently disclosed vulnerabilities that may not yet have exploits
“Has Exploit” Filter
The most important filter for OSCP: check “Has Exploit” to show only CVEs that have known public exploits. This saves time by filtering out theoretical vulnerabilities.
2.4 Practical OSCP Example
Scenario: You discover Oracle WebLogic Server 12.2.1.3 on port 7001
1. Go to cvedetails.com
2. Vendor: Oracle
3. Product: WebLogic Server
4. Version: 12.2.1.3
5. Filter: Has Exploit = Yes, Severity >= 7.0
6. Result: CVE-2020-14882 (CVSS 9.8) - Deserialization RCE
7. Click CVE → see exploit references
8. Search Exploit-DB for CVE-2020-14882
9. Find and test the exploit
3. NVD (National Vulnerability Database)
3.1 Overview
The National Vulnerability Database (https://nvd.nist.gov) is the official US government maintained repository of CVE entries. It provides standardized vulnerability descriptions, CVSS scores, and CPE-based product matching.
| Attribute | Detail |
|---|---|
| URL | https://nvd.nist.gov |
| Authority | NIST (National Institute of Standards and Technology) |
| Content | Official CVE entries with standardized metadata |
| API | REST API available (requires free API key) |
| OSCP Relevance | Medium-High — best for authoritative CVE details and CPE matching |
3.2 Advanced Search Parameters
The NVD Advanced Search (https://nvd.nist.gov/feeds/json/cve/1.1/) supports:
| Parameter | Description | Example |
|---|---|---|
| CVE ID | Direct CVE lookup | CVE-2021-41773 |
| CWE | Common Weakness Enumeration | CWE-79 (XSS), CWE-89 (SQLi) |
| CVSS Version | v2.0, v3.0, v3.1, v4.0 | v3.1 |
| CVSS Score | Score range filter | 7.0 to 10.0 |
| CPE | Common Platform Enumeration | cpe:2.3:a:apache:http_server:2.4.49:::::::* |
| Publish Date | Date range for publication | 2024-01-01 to 2024-12-31 |
| Last Modified | Date range for last update | 2024-06-01 to 2024-12-31 |
| Keywords | Free-text search | “path traversal”, “remote code execution” |
| EPSS Score | Exploit Prediction Scoring System | >= 0.5 (50%+ exploit probability) |
3.3 CPE Integration
CPE (Common Platform Enumeration) is the NVD’s standardized product identification system. Understanding CPE is essential for precise vulnerability matching.
CPE 2.3 Format:
cpe:2.3:<part>:<vendor>:<product>:<version>:<update>:<edition>:<language>:<sw_edition>:<target_sw>:<target_hw>:<other>
Part types:
a= Application (software)o= Operating Systemh= Hardware
Real examples:
# Apache HTTP Server 2.4.49
cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
# Microsoft Windows 10 version 2004
cpe:2.3:o:microsoft:windows_10:2004:*:*:*:*:*:*:*
# OpenSSH 8.2p1
cpe:2.3:a:openbsd:openssh:8.2p1:*:*:*:*:*:*:*
# Using wildcards for version ranges
cpe:2.3:a:apache:http_server:2.4:*:*:*:*:*:*:*
# Matches ALL Apache HTTP Server 2.4.x versions
Using CPE in NVD searches:
- Go to https://nvd.nist.gov/products/cpe/search
- Enter vendor and product name
- Find the correct CPE string
- Use the CPE in Advanced Search to find all associated CVEs
3.4 NVD API Access
The NVD provides a free REST API for programmatic vulnerability lookup:
# Get API key (free): https://nvd.nist.gov/developers/request-an-api-key
# Search for a specific CVE
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-41773"
# Search by CPE
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=apache+http+server+2.4.49"
# Search with CVSS filter
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://services.nvd.nist.gov/rest/json/cves/2.0?cvssV3Severity=HIGH"
3.5 How to Use NVD During OSCP
The NVD is most valuable during OSCP for:
- Confirming CVE details — When you find a CVE reference in an exploit, verify the affected versions on NVD
- Finding related CVEs — Search by CPE to discover all vulnerabilities for a specific product version
- Understanding severity — CVSS scores help prioritize which exploits to attempt first
- EPSS scores — The Exploit Prediction Scoring System tells you the probability that a vulnerability will be exploited in the wild (higher = more likely to have working exploits)
Quick NVD workflow during exam:
1. Identify target: Apache 2.4.49
2. Go to nvd.nist.gov
3. Search: "Apache HTTP Server 2.4.49"
4. Review CVEs sorted by CVSS score (highest first)
5. Note CVE IDs with CVSS >= 7.0
6. Cross-reference each CVE on Exploit-DB for available exploits
4. GitHub Exploit Repositories
4.1 Overview
GitHub has become a major hub for exploit code, especially for:
- Zero-day exploits before they reach Exploit-DB
- Custom/modified exploits adapted for specific targets
- Proof-of-concept (PoC) code from security researchers
- Automated exploit frameworks and tooling
4.2 Major Repositories and Collections
| Repository | URL Pattern | Focus | Quality |
|---|---|---|---|
| Exploit-DB Mirrors | Various | Complete Exploit-DB dumps | High |
| Metasploit External Modules | metasploit/external-modules |
Community Metasploit modules | High |
| Sploitus Mirror | Various | Aggregated exploits from multiple sources | Medium |
| 0day Exploits | Various | Recent zero-day disclosures | Variable |
| Personal Researcher Repos | Various | Individual researcher work | Variable |
| CVE PoC Collections | Various | PoC code organized by CVE | Variable |
| Project Zero | google/project-zero |
Google’s security research | Very High |
| Nuclei Templates | projectdiscovery/nuclei-templates |
Vulnerability detection templates | High |
4.3 GitHub Search Syntax
Master GitHub’s search syntax to find exploit code efficiently:
# === Basic Exploit Searches ===
site:github.com "CVE-2021-41773" exploit
site:github.com "Apache" "path traversal" exploit
# === Advanced Search Operators ===
# Search in file names and paths
"CVE-2021-41773" in:path
# Filter by programming language
"exploit" "apache" language:python
"exploit" "apache" language:ruby
# Filter by stars (community validation)
"exploit" "printnightmare" stars:>10
# Filter by recency
"exploit" "log4j" pushed:>2021-12-01
# Combine multiple filters
"CVE-2023-XXXXX" exploit language:python stars:>5 pushed:>2023-01-01
# Search in README files
"exploit" "windows" "privilege escalation" in:readme
# Exclude terms
"exploit" "apache" -metasploit
Direct GitHub search URL:
https://github.com/search?q=%22CVE-2021-41773%22+exploit&type=code
4.4 Finding Exploit PRs and Forks
Pull Requests (PRs):
- Search for PRs that add exploit modules to frameworks
- These often contain well-tested, reviewed code
- Example: Search
is:pr "exploit" "CVE-2024-XXXXX"on GitHub
Forks:
- Forks of exploit repositories often contain fixes and improvements
- Check the “Forks” tab on popular exploit repos
- Compare fork commits against the original for bug fixes
4.5 Quality Indicators for GitHub Exploits
| Indicator | What to Look For | Why It Matters |
|---|---|---|
| Stars | 10+ stars = community interest | More stars = more people have reviewed/tested |
| Forks | Active forking = adaptation in progress | Shows the exploit is being used and improved |
| Issues | Open issues may reveal bugs | Check if others report failures |
| Comments | PR/discussion comments | Community feedback on reliability |
| Commit History | Recent commits = active maintenance | Actively maintained exploits are more reliable |
| README Quality | Detailed usage instructions | Well-documented exploits are easier to adapt |
| Contributors | Multiple contributors | Diverse testing across environments |
| Organization | Published by known security orgs | Project Zero, Trail of Bits, etc. = high quality |
4.6 OSCP-Specific GitHub Tips
- Search by CVE first — The most reliable GitHub search pattern is
"CVE-YYYY-NNNNN" exploit - Check the
projectdiscovery/nuclei-templatesrepo — Contains detection templates for thousands of vulnerabilities - Look for
exploitin the filename — Many researchers name files descriptively:CVE-2021-41773_exploit.py - Beware of outdated repos — Check the last commit date; exploits older than 1-2 years may not work
- Read the README — Many GitHub exploits include usage instructions, prerequisites, and known limitations
5. Packet Storm Security
5.1 Overview
Packet Storm Security (https://packetstormsecurity.com) is one of the oldest and most respected security resource sites, founded in 1995. It provides a broad collection of security-related content beyond just exploits.
| Attribute | Detail |
|---|---|
| URL | https://packetstormsecurity.com |
| Founded | 1995 |
| Content | Exploits, advisories, papers, tools, warnings |
| Update Frequency | Multiple times daily |
| OSCP Relevance | Medium — useful supplement to Exploit-DB |
5.2 Content Categories
| Category | Description | When to Use |
|---|---|---|
| Exploits | Remote and local exploit code | When Exploit-DB has no results |
| Advisories | Vendor security announcements | Understanding vulnerability context |
| Papers | Technical research documents | Deep understanding of vulnerability mechanics |
| Tools | Security utilities and scanners | Finding auxiliary tools for exploitation |
| Warnings | Urgent security notifications | Staying aware of critical vulnerabilities |
| Files | Miscellaneous security files | Additional resources |
5.3 Search Strategy
- Use category filters — Navigate to the specific category (e.g., “Exploits”) before searching
- Sort by date — Latest vulnerabilities appear first
- Use the search box — Search by product name, CVE ID, or vulnerability type
- Check advisories — Read vendor advisories for context on affected versions
- Review papers — Technical papers often explain the vulnerability in depth, helping you understand and adapt exploits
5.4 When to Use Packet Storm Over Exploit-DB
Use Packet Storm when:
- Exploit-DB has no results — Packet Storm sometimes has exploits not yet on Exploit-DB
- You need context — The advisory and paper sections provide deeper understanding
- You need tools — The tools section has scanners and utilities not found elsewhere
- You want early access — Some exploits appear on Packet Storm before Exploit-DB
- You need research papers — Understanding the vulnerability mechanics helps with exploit adaptation
5.5 Practical Example
Scenario: You find a vulnerability in a proprietary product not well-covered by Exploit-DB
1. Go to packetstormsecurity.com
2. Navigate to "Exploits" category
3. Search for the product name
4. If no exploit found, check "Advisories" for vulnerability details
5. Check "Papers" for technical analysis
6. Use the information to search Exploit-DB and GitHub with better keywords
6. 0day.today
6.1 Overview
0day.today (https://0day.today) is an exploit aggregation site that collects exploits from multiple sources including Exploit-DB, Packet Storm, and other security feeds. It provides a quick, unified interface for browsing exploit code.
| Attribute | Detail |
|---|---|
| URL | https://0day.today |
| Content | Aggregated exploits from multiple sources |
| Key Feature | Unified search across multiple databases |
| OSCP Relevance | Low-Medium — supplementary resource |
6.2 How to Use It Safely
0day.today is convenient but requires extra caution:
- Always verify exploit reliability — Aggregated content may include unverified or outdated exploits
- Cross-reference with Exploit-DB — Check if the same exploit exists on Exploit-DB with community feedback
- Review the code carefully — Examine the exploit source before execution
- Check the source attribution — 0day.today usually indicates the original source (Exploit-DB, Packet Storm, etc.)
- Verify the CVE references — Confirm CVE details on NVD or CVE Details
6.3 Verification Requirements
Before using any exploit from 0day.today:
| Check | Action |
|---|---|
| Source verification | Confirm the exploit exists on the original source (Exploit-DB/Packet Storm) |
| Code integrity | Compare the code with the original source to ensure no tampering |
| Version matching | Verify the exploit targets your exact target version |
| Community feedback | Check Exploit-DB comments for success/failure reports |
| Date validation | Ensure the exploit is recent enough to be relevant |
6.4 When 0day.today Is Useful
- Quick cross-reference — See if an exploit exists across multiple databases
- Discovery — Find exploits you might have missed on individual databases
- Convenience — Single interface for browsing multiple sources
7. SecurityFocus / BID Database
7.1 Overview
SecurityFocus (now part of Tenable) maintained the BID (Bugtraq ID) database, one of the earliest vulnerability tracking systems. While its prominence has diminished, it remains relevant for historical vulnerability research.
| Attribute | Detail |
|---|---|
| URL | https://www.securityfocus.com (now integrated with Tenable) |
| Content | Vulnerability descriptions, BID entries, exploit references |
| BID Format | BID-XXXXX (e.g., BID-49534) |
| OSCP Relevance | Low — mainly historical reference |
7.2 BID Database
BID (Bugtraq ID) entries provide:
- Detailed vulnerability descriptions — Often more verbose than CVE descriptions
- Exploit availability indicators — Whether public exploits exist
- Patch information — Links to vendor patches and fixes
- Cross-references — Links to CVE IDs and other databases
- Historical context — Long-standing tracking since the late 1990s
7.3 When SecurityFocus Is Relevant
- Historical vulnerabilities — Older CVEs may have better documentation in BID entries
- Cross-referencing — Some older exploits reference BID instead of CVE
- Vendor advisory context — BID entries often link to original vendor advisories
- Tenable integration — If you use Nessus (Tenable), BID references appear in scan results
8. Other Resources
8.1 FullHunt
FullHunt (https://fullhunt.io) is an attack surface management platform that also maintains a vulnerability database.
- Strengths: Real-world exploit intelligence, attack surface data
- OSCP Use: Limited — more valuable for bug bounty and enterprise assessments
- Key Feature: Shows which vulnerabilities are actively being exploited in the wild
8.2 Vulmon
Vulmon (https://www.vulmon.com) is a vulnerability intelligence platform aggregating data from multiple sources.
- Strengths: Aggregates CVE, Exploit-DB, NVD, and vendor advisory data
- Search: Advanced filtering by vendor, product, version, and exploit availability
- OSCP Use: Good supplementary search when Exploit-DB returns limited results
- Key Feature: “ExploitDB” tab on each CVE page directly links to available exploits
8.3 ExploitSearch
ExploitSearch (https://exploitsearch.io) provides a search interface for exploit databases.
- Strengths: Simple, fast search across multiple exploit sources
- OSCP Use: Quick lookup when you need fast results
- Key Feature: Direct links to exploit code and source databases
8.4 Snyk Vulnerability Database
Snyk (https://snyk.io/vuln/) focuses on software dependency vulnerabilities.
- Strengths: Excellent for library/package vulnerabilities (npm, pip, Maven, etc.)
- OSCP Use: Useful when targeting applications with known vulnerable dependencies
- Key Feature: Shows vulnerable version ranges and fix versions clearly
8.5 Additional Resources
| Resource | URL | Best For |
|---|---|---|
| MITRE ATT&CK | https://attack.mitre.org | Understanding attack techniques and mappings |
| CWE List | https://cwe.mitre.org | Understanding vulnerability classes |
| Sploitus | https://sploitus.com | Aggregated exploit search |
| SecLists | https://github.com/danielmiessler/SecLists | Wordlists, payloads, and data for testing |
| Pentest Monkey | https://pentestmonkey.net | Privilege escalation guides and one-liners |
| GTFOBins | https://gtfobins.github.io | Linux privilege escalation via binaries |
| Windows Exploit Suggester | Various GitHub repos | Windows missing patch analysis |
9. Resource Comparison Table
| Resource | Best For | Search Quality | Exploit Quality | Speed | OSCP Value | Free? |
|---|---|---|---|---|---|---|
| Exploit-DB | Everything — your primary resource | Excellent | High (curated) | Fast | Critical | Yes |
| CVE Details | Vendor/product/version filtering | Excellent | N/A (metadata only) | Fast | High | Yes |
| NVD | Authoritative CVE details, CPE matching | Very Good | N/A (metadata only) | Medium | Medium-High | Yes |
| GitHub | Zero-days, custom exploits, PoCs | Good (with skill) | Variable | Medium | Medium-High | Yes |
| Packet Storm | Early exploits, papers, tools | Good | Medium-High | Medium | Medium | Yes |
| 0day.today | Quick cross-reference | Good | Variable | Fast | Low-Medium | Yes |
| SecurityFocus/BID | Historical vulnerabilities | Medium | N/A (metadata only) | Slow | Low | Yes |
| Vulmon | Aggregated intelligence | Good | N/A (links to sources) | Medium | Low-Medium | Yes |
| FullHunt | Real-world exploit intel | Good | N/A (intelligence) | Medium | Low | Freemium |
| Snyk | Dependency vulnerabilities | Good | N/A (metadata only) | Fast | Low | Freemium |
Pros and Cons Summary
| Resource | Pros | Cons |
|---|---|---|
| Exploit-DB | Authoritative, curated, searchsploit integration, community feedback | May lag behind GitHub for very new exploits |
| CVE Details | Best vendor/product filtering, version precision, exploit availability flag | No exploit code — metadata only |
| NVD | Official/authoritative, CPE precision, API access, EPSS scores | Complex interface, no exploit code |
| GitHub | Latest exploits, custom adaptations, active community | Variable quality, requires search skill, noise |
| Packet Storm | Early access, papers/tools, long history | Less curated than Exploit-DB, older interface |
| 0day.today | Unified aggregation, quick browsing | Unverified content, requires cross-referencing |
| SecurityFocus | Historical depth, BID cross-references | Diminished relevance, slower updates |
10. Which Resources Are Most Valuable for OSCP?
Tier 1: Essential (Use on Every Exam)
| Resource | Why |
|---|---|
| Exploit-DB + Searchsploit | Your primary exploit source. Pre-installed on Kali. Fast, reliable, curated. This is 80% of your exploit research. |
| CVE Details | Best for initial vulnerability identification. Vendor/product/version filtering saves time. |
Tier 2: Important (Use When Tier 1 Falls Short)
| Resource | Why |
|---|---|
| GitHub | When Exploit-DB has no results, or you need a more recent/custom exploit. Essential for zero-days. |
| NVD | For authoritative CVE verification and CPE-based searches. |
| Packet Storm | When you need papers for understanding, or exploits not yet on Exploit-DB. |
Tier 3: Supplementary (Rarely Needed)
| Resource | Why |
|---|---|
| 0day.today | Quick cross-reference when you’re unsure if an exploit exists |
| Vulmon | Aggregated view when you want to check multiple sources at once |
| SecurityFocus/BID | Historical reference for older vulnerabilities |
Recommended OSCP Exploit Research Workflow
┌─────────────────────────────────────────────────────────────┐
│ OSCP EXPLOIT WORKFLOW │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. Enumerate → Identify service + exact version │
│ ↓ │
│ 2. CVE Details → Vendor → Product → Version → Has Exploit? │
│ ↓ │
│ 3. Searchsploit → Exact version → Broaden if needed │
│ ↓ │
│ 4. Evaluate → Quality checklist → Pick top 2-3 candidates │
│ ↓ │
│ 5. GitHub → Search by CVE → Check for newer/better exploits│
│ ↓ │
│ 6. NVD → Verify CVE details, affected versions, CVSS │
│ ↓ │
│ 7. Test → Lab environment first → Adapt if needed │
│ ↓ │
│ 8. Execute → Against target → Document results │
│ │
└─────────────────────────────────────────────────────────────┘
Time Management Tips for Exam
- Spend no more than 15-20 minutes on exploit research for a single service before moving on
- Start with searchsploit — it’s the fastest and most reliable
- If searchsploit returns nothing, try CVE Details → GitHub → Packet Storm in that order
- Don’t get stuck — if an exploit isn’t working after 10 minutes of debugging, try a different exploit or a different attack vector
- Document your research — even failed exploit attempts are worth noting in your report
Quick Reference Cheat Sheet
Essential URLs
| Resource | URL |
|---|---|
| Exploit-DB | https://www.exploit-db.com |
| CVE Details | https://www.cvedetails.com |
| NVD | https://nvd.nist.gov |
| Packet Storm | https://packetstormsecurity.com |
| 0day.today | https://0day.today |
| Vulmon | https://www.vulmon.com |
| GitHub | https://github.com |
| GTFOBins | https://gtfobins.github.io |
| SecLists | https://github.com/danielmiessler/SecLists |
Essential Commands
# Exploit-DB / Searchsploit
searchsploit --update # Update local database
searchsploit <keyword> # Basic search
searchsploit -w "term1" "term2" # Wildcard search
searchsploit -p <platform> <keyword> # Platform filter
searchsploit -t <type> <keyword> # Type filter
searchsploit -m <EDB-ID> # Mirror single exploit
searchsploit -mm <keyword> # Mirror all matching exploits
searchsploit -x <EDB-ID> # Open in editor
# Git clone (offline access)
git clone https://gitlab.com/exploit-database/exploitdb.git
# NVD API
curl -H "Authorization: Bearer KEY" "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-41773"
# GitHub search
# Use browser: https://github.com/search?q=%22CVE-YYYY-NNNNN%22+exploit&type=code
Exploit Quality Checklist
- EDB-ID age: 1-8 weeks ideal
- Author: Known researcher preferred
- Comments: Positive community feedback
- Tested On: Matches your target environment
- Code: Clean, commented, error handling
- CVE: Referenced and verified on NVD
- Dependencies: Clear and available
- Language: Python/Ruby preferred (easy to modify)