Aller au contenu

ExploitDB Binary Sploits

ExploitDB Binary Sploits (exploitdb-bin-sploits) is a collection of pre-compiled exploit binaries maintained by Exploit-DB. These are ready-to-run exploits for various vulnerabilities, organized by platform and application type. Used in authorized penetration testing engagements to quickly deploy exploits without compilation.

Important: Only use these exploits in authorized penetration testing and research. Unauthorized access to computer systems is illegal.

# Clone the repository
git clone https://github.com/offensive-security/exploitdb-bin-sploits.git
cd exploitdb-bin-sploits

# List directory structure
ls -la
# Using Git Bash or WSL
git clone https://github.com/offensive-security/exploitdb-bin-sploits.git
cd exploitdb-bin-sploits
# Run in container (useful for isolated testing)
docker pull kalilinux/kali-linux-docker
docker run -it -v /path/to/exploitdb-bin-sploits:/sploits kalilinux/kali-linux-docker
# View top-level organization
tree -L 2 exploitdb-bin-sploits/

# Typical structure:
# exploitdb-bin-sploits/
# ├── Linux/
# │   ├── Privilege Escalation/
# │   ├── Local Exploits/
# │   └── Remote Exploits/
# ├── Windows/
# │   ├── Privilege Escalation/
# │   ├── Local Exploits/
# │   └── Remote Exploits/
# ├── macOS/
# ├── Web Applications/
# └── Denial of Service/
# Kali Linux automatically integrates binary sploits
searchsploit --nmap /path/to/nmap.xml

# Find binaries matching a vulnerability
searchsploit -t Apache 2.4.49 --bin
# Add custom path to searchsploit database
export SEARCHSPLOIT_PATH="/path/to/exploitdb-bin-sploits"
searchsploit apache
# Update exploit database (includes binary references)
searchsploit -u

# Sync with Exploit-DB repository
cd /usr/share/exploitdb && git pull
# List all Linux exploits
ls -la Linux/Local\ Exploits/
ls -la Linux/Privilege\ Escalation/

# Find specific Linux binary
find . -name "*linux*" -type f | head -20

# View binary metadata
file Linux/Privilege\ Escalation/*/exploit_binary
# List Windows exploits (typically .exe files)
ls -la Windows/

# Find by type
find . -path "*Windows*" -name "*.exe" | sort

# Check binary architecture
file Windows/*/exploit.exe
# List web app exploits
ls -la "Web Applications/"

# Find by vulnerability type
find . -path "*Web*" -type f

# Common categories
find . -path "*SQL Injection*" -o -path "*XSS*" -o -path "*RCE*"
# Search Exploit-DB database by CVE
searchsploit CVE-2021-3156

# Find associated binary
searchsploit CVE-2021-3156 --bin

# View full entry with binary path
searchsploit CVE-2021-3156 -p
# Check exploit metadata (if available)
cat "Linux/Privilege Escalation/CVE-2021-3156/README.txt"

# Link to Exploit-DB page
# Format: https://www.exploit-db.com/exploits/[EDB-ID]
# Example: https://www.exploit-db.com/exploits/49488
CVE ClassLocationUse Case
Linux Privilege EscalationLinux/Privilege Escalation/Post-exploitation
Windows Local ExploitWindows/Local Exploits/Client-side attacks
Remote Code Execution*/Remote Exploits/Initial access
Denial of ServiceDenial of Service/DoS testing
Web App VulnerabilityWeb Applications/Application testing
# Browse local exploits
ls -la "Linux/Local Exploits/"

# Check exploit type
file "Linux/Local Exploits/CVE-*/exploit"

# Common targets: sudo, kernel, SUID binaries
# List remote exploitation binaries
ls -la "Linux/Remote Exploits/"

# Target network services
find . -path "*Remote*" -type f

# Check service type (HTTP, SSH, FTP, etc.)
# Web app specific exploits
ls -la "Web Applications/"

# Common frameworks: WordPress, Joomla, Apache, Nginx
find . -path "*Web*" -name "*WordPress*"
# DoS attack binaries
ls -la "Denial of Service/"

# Check protocol types (TCP, UDP, DNS, etc.)
file "Denial of Service"/*
# Scan target system
nmap -sV -p- target.com > nmap_scan.txt

# Identify services and versions
grep "open" nmap_scan.txt
# Method 1: Use searchsploit
searchsploit "Apache 2.4.49"

# Method 2: Browse directory manually
find . -name "*apache*" -o -name "*2.4*"

# Method 3: CVE lookup
searchsploit CVE-2021-41773
# Get full path from searchsploit
searchsploit "Apache 2.4.49" -p

# Or navigate directly
ls -la "Web Applications/Apache 2.4.49/"
# Copy to working directory
cp "Web Applications/Apache 2.4.49/exploit" ./

# Make executable
chmod +x exploit

# Check dependencies
ldd exploit
# Run exploit (check documentation first)
./exploit -h

# Execute with parameters
./exploit -t "http://target.com" --payload bind_shell

# Capture output
./exploit -t target.com > exploit_results.txt 2>&1
# Record successful exploitation
echo "CVE-2021-41773 | Apache 2.4.49 | RCE successful" >> exploitation_log.txt

# Archive evidence
tar -czf exploitation_evidence.tar.gz exploit_results.txt
# Verify binary is executable
ls -la exploit

# Check binary type
file exploit
# Expected output: ELF 64-bit LSB executable (Linux) or PE32 (Windows)

# Check dependencies
ldd exploit
# Verify all dependencies are available

# Inspect for malware (optional)
strings exploit | head -20
# Check target architecture
uname -m

# Match binary architecture
file Linux/Privilege\ Escalation/*/exploit
# Look for: x86_64 (64-bit) or i386 (32-bit)

# Cross-compile if needed
gcc -m32 exploit.c -o exploit_32bit
# View available parameters
./exploit -h
./exploit --help

# Common parameters
./exploit -t target_host
./exploit -p 80
./exploit -u username -p password

# Background execution (post-exploitation)
./exploit -t target &
nohup ./exploit -t target > output.log &
# Create local mirror
rsync -av exploitdb-bin-sploits/ /backup/exploitdb-bin-sploits/

# Compress for storage
tar -czf exploitdb-bin-sploits-backup.tar.gz exploitdb-bin-sploits/

# Verify backup integrity
sha256sum exploitdb-bin-sploits-backup.tar.gz
# Generate index of all binaries
find . -type f -executable > all_exploits.txt

# Index by type
find . -path "*Privilege*" -type f > privesc_exploits.txt
find . -path "*Remote*" -type f > remote_exploits.txt

# Tag with CVE references
grep -r "CVE-" . > cve_index.txt
# Binary may not execute on different OS versions
# Test in isolated environment first

# Check glibc requirements
ldd exploit | grep libc

# If dependencies missing, compile from source
# Most exploits available as source code on Exploit-DB
# Pre-compiled binaries may trigger AV detection
# Scan binary before deployment
clamscan exploit

# Consider obfuscation or custom compilation
# Use polymorphic wrappers if available
# Always obtain written authorization before testing
# Document authorized scope in Rules of Engagement (RoE)
# Maintain responsible disclosure timeline

# Log all exploitation attempts
echo "[$(date)] Exploit: CVE-X | Target: Y | Result: Z" >> engagement_log.txt
# Check permissions
chmod +x exploit

# Verify correct architecture
file exploit
uname -m

# Check for missing dependencies
ldd exploit

# Run with verbose output
strace ./exploit -t target
# Binary compiled for different architecture/OS version
# Find alternative binary
find . -name "exploit*" | xargs file

# Compile from source instead
searchsploit -m 12345  # Download source code
# Check if running with sufficient privileges
whoami
id

# Privilege escalation may be required
# Many local exploits need to run as regular user
ResourcePurpose
Official Exploit-DBBrowse and verify exploits
searchsploit man pageCLI usage documentation
Kali Linux documentationIntegration guides
GitHub repositoryBug reports and updates