WEBVTT

00:07.680 --> 00:11.220
Hello, guys, and welcome to the
second video of this chapter.

00:11.250 --> 00:13.860
SSL stripping, as the name implies,

00:13.890 --> 00:20.460
is an Attack that uses the SSL strip tool
or a related techniques to strip away the

00:20.490 --> 00:26.940
protection provided by the
SSL TLS Protocol and HTTPS.

00:26.970 --> 00:31.200
It's a form of man in
the middle Attack that takes advantage of

00:31.230 --> 00:36.840
the TLS protocol and the
way it begins connections.

00:37.080 --> 00:38.960
To understand everything, we are going to

00:38.990 --> 00:44.820
need to start with HTTPs
and man in the middle Attack.

00:44.850 --> 00:47.000
When the World Wide Web was first

00:47.030 --> 00:54.120
conceived, it wasn't intended for commerce
or other vital services, it was a way for

00:54.150 --> 00:57.860
the government and the
academia to share information.

00:57.890 --> 01:02.020
And that didn't require much security.

01:02.050 --> 01:04.740
When the Internet was commercialized,

01:04.770 --> 01:10.280
security and privacy became key
considerations, the creation of the Secure

01:10.310 --> 01:16.410
Sockets Layer SSL protocol was
the first attempt as an answer.

01:16.440 --> 01:22.260
It made connections via secure channel,
the port four four three and layered

01:22.290 --> 01:26.980
encryption over connections
at the application level.

01:27.010 --> 01:33.820
This was known as HTTP over SSL, or
as is better known today, HTTPs.

01:33.850 --> 01:36.740
But SSL was float.

01:36.770 --> 01:39.850
And was quickly found to be vulnerable,

01:39.880 --> 01:49.180
SSL 3.0 was replaced with Transport
Layer Security TLS 1.0 in 1999.

01:49.210 --> 01:54.360
The key difference was that TLS began
connections with a hello via and insecure

01:54.390 --> 02:00.490
channel before being
redirected to a secure one.

02:00.520 --> 02:03.480
Both use port four four, three and encrypt

02:03.510 --> 02:09.100
HTTP connections, but the genesis
of those connections differed.

02:09.130 --> 02:13.260
And that's where SSL stripping comes in.

02:13.290 --> 02:17.860
So when you connect to a Website, your
connection has to be routed through

02:17.890 --> 02:24.170
multiple and dozens of other points on
its way to reach the desired destination.

02:24.200 --> 02:27.660
If you are not using Encryption.

02:27.690 --> 02:32.560
HTTPS in particular,
all the data you are transmitting over the

02:32.590 --> 02:37.340
connection passes through each one of
those points in Plaintext,

02:37.370 --> 02:41.840
that means anyone that is eavesdropping at
one of those points can effectively

02:41.870 --> 02:48.020
intercept the read and even manipulate
everything that is being communicated.

02:48.050 --> 02:52.340
The answer to this has historically been
to encrypt the connection.

02:52.370 --> 02:54.680
So even if someone is eavesdropping the

02:54.710 --> 03:02.460
data, is in the cipher text and unreadable
to the attacker, so therefore

03:02.490 --> 03:06.420
SSL stripping is a workaround
for that Encryption.

03:06.450 --> 03:09.120
So we discussed earlier how TLS begins

03:09.150 --> 03:14.740
within nsecure hello, before it's
redirected to a secure channel.

03:14.770 --> 03:20.480
So if a man in the middle attacker can
redirect the client to an HTTP version of

03:20.510 --> 03:25.740
the Website, it can steal information
and manipulate the connection.

03:25.770 --> 03:28.420
There are several ways this can be done.

03:28.450 --> 03:30.720
The easiest is probably to set up a

03:30.750 --> 03:38.660
proofed Wi-fi network in a public setting
and Attack the people who login into it.

03:38.690 --> 03:43.340
You can also compromise a point somewhere
in the middle of the connection.

03:43.370 --> 03:49.420
Because that initial hello, I'm HTTP
direction, the quest is encrypted.

03:49.450 --> 03:52.020
Because that initial hello and HTTP

03:52.050 --> 03:56.940
Directory request is unencrypted,
a man in the middle.

03:56.970 --> 04:02.610
Can alter it and send the user to
an insecure version of that page.

04:02.640 --> 04:06.840
Keep in mind, however, that when you
install a SSL, you are essentially

04:06.870 --> 04:12.220
creating a duplicate of your Website
with HTTPS URLs.

04:12.250 --> 04:17.720
Those original HTTP URL still exist,
though, usually use three zero one or

04:17.750 --> 04:23.560
three zero two redirects to ensure users
can reach the HTTP Website, but if an

04:23.590 --> 04:29.340
attacker can manipulate the redirect, they
can still send the user to that page.

04:29.360 --> 04:34.040
Now, the user is still on your site,
interacting as they normally would, but

04:34.070 --> 04:38.740
every bit of data
retransmit is in Plaintext.

04:38.770 --> 04:43.220
In SSL stripping Attack
Attack character as a Breach.

04:43.250 --> 04:46.160
It's making an HTTPS connection with a

04:46.190 --> 04:51.460
Server and an HTTP
connection with a client.

04:51.480 --> 04:56.820
That makes the connection appear secure,
almost as if you were using the VPN, but

04:56.840 --> 05:00.100
the Attacker is still in
the data in this case.

05:00.130 --> 05:06.380
So there are two main tactics that
can be used to avoid such attacks.

05:06.410 --> 05:09.540
You can use only the latest TLS protocol

05:09.570 --> 05:15.220
version and/or
Website to the HSTS preload list,

05:15.250 --> 05:19.960
data engineering task force
and the creators of TLS have worked very

05:19.980 --> 05:27.220
hard to shore up this problem
as one point two and never more. TLS

05:27.250 --> 05:33.100
one point three have been designed to
be resistant to this kind of attacks.

05:33.130 --> 05:36.540
They encrypt more of the handshake.

05:36.570 --> 05:43.480
The portion where the connection is
redirected already TLS 2.0 and 3.0 have

05:43.510 --> 05:49.620
been fully deprecated and the major tech
companies have announced plans to hold

05:49.650 --> 05:57.740
fully deprecate TLS 1.0 at one
point one by January twenty twenty.

05:57.770 --> 06:04.900
This is for good reason, TLS 1.2 an even
more so TLS one point three is superior.

06:04.920 --> 06:08.960
The other thing you can do is hold your
Website, as we mentioned earlier, to the

06:08.980 --> 06:12.860
HTTP Strict Transport Security
preload list

06:12.890 --> 06:18.200
you should already be using HSTS,
which is an HTTP header that forces the

06:18.230 --> 06:21.020
client to make a secure
connection to the Website.

06:21.040 --> 06:23.800
If the client can return HTTPS version of

06:23.830 --> 06:28.960
the site, it just doesn't connect at
the HSTS needed to download it first.

06:28.980 --> 06:32.200
So the very first time a client arrives at

06:32.230 --> 06:36.720
your Website, there is a small Attack
vector for an attacker to SSL strip.

06:36.750 --> 06:40.220
The HSTS preload list closes this window.

06:40.250 --> 06:42.420
Once your site is included, any client

06:42.450 --> 06:48.260
will know to only make secure connections,
even if they never visited the site.

06:48.290 --> 06:49.940
So that's all for this video.

06:49.960 --> 06:51.800
You can just go ahead now and click on the

06:51.830 --> 06:54.720
next video call Detecting
Christmas Tree Attack.

