SSL Stripping
Also called HTTPS downgrade.
Downgrading a victim's HTTPS connection to plaintext HTTP.
What it is
An on-path attack that intercepts a user's attempt to reach a secure site and quietly keeps the victim on plaintext HTTP while the attacker maintains HTTPS to the real server. The user never gets the encryption they expected.
Why it matters
Stripping exposes credentials and session data the victim assumed were protected. It specifically exploits the gap before protections like HSTS take effect, so investigators confirm HSTS status when working an account-takeover case.
In practice
Finding that a victim's login posted over cleartext HTTP because an on-path attacker had stripped the redirect to HTTPS.
What to look for
- HTTP requests to sites that should use HTTPS.
- Missing HSTS headers on your sites.
- Login forms submitted over plain HTTP.
Common mistake
Leaving HSTS off. Without it, the first visit can be downgraded.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
- Network Case
A host suspected of beaconing: work its capture from scope to beacon, then the port recall and subnet math behind it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Man-in-the-Middle: Secretly relaying and possibly altering traffic between two parties.
- ARP Spoofing: Forging ARP replies to intercept traffic on a local network.
- SNI Inspection: Reading the destination hostname from the TLS handshake.