SSL Stripping Attacks
What you'll learn: How attackers downgrade secure HTTPS connections to insecure HTTP, letting them read or modify encrypted traffic.
The Core Problem
You've learned how to position yourself as a man-in-the-middle using ARP spoofing. Now imagine the victim tries to visit their bank at https://bank.com. Normally, all communication would be encrypted with TLS/SSL, protecting it from your prying eyes.
SSL stripping solves this problem (from an attacker's perspective) by downgrading the connection. Instead of letting the victim use HTTPS, you intercept the initial connection and strip away the secure protocol, forcing them to use plain HTTP instead—all while you maintain the HTTPS connection to the real server.
How It Works
- Victim requests a website (often by typing
bank.comwithout explicitly typing "https://") - Your MITM position intercepts this request before it reaches the real server
- You connect to the real server via HTTPS (the secure connection)
- You send the victim an HTTP version of the page (insecure)
- All links on the page are rewritten from
https://tohttp:// - The victim browses thinking everything is normal, but their traffic flows through you in plain text
- You relay their requests/responses, reading passwords, session cookies, and sensitive data
The Deception
Think of it like a dishonest translator. The victim speaks to you in plain language (HTTP), you translate it to encrypted language for the bank (HTTPS), then translate the bank's encrypted response back to plain language for the victim. The victim never realizes the "translation" is betraying their privacy.
Key Takeaway:
SSL stripping downgrades HTTPS to HTTP by intercepting connections and rewriting protocols, allowing attackers to read encrypted traffic in plain text while maintaining the secure connection to the real server themselves.