WEBVTT

00:00:00.000 --> 00:00:09.780 align:middle line:90%


00:00:09.780 --> 00:00:11.430 align:middle line:84%
In this lab, we're
going to take some

00:00:11.430 --> 00:00:15.120 align:middle line:84%
of what we've learned with
Wireshark and network traffic

00:00:15.120 --> 00:00:16.950 align:middle line:84%
and we're actually
going to make an attack.

00:00:16.950 --> 00:00:18.533 align:middle line:84%
We're going to do a
man in the middle.

00:00:18.533 --> 00:00:20.640 align:middle line:84%
We're going to do
some ARP poisoning.

00:00:20.640 --> 00:00:23.790 align:middle line:84%
So let's get into the
environment and play with that.

00:00:23.790 --> 00:00:29.680 align:middle line:90%


00:00:29.680 --> 00:00:31.900 align:middle line:90%
We have our console.

00:00:31.900 --> 00:00:34.330 align:middle line:84%
Let's check out our
IP address on ETH1.

00:00:34.330 --> 00:00:36.040 align:middle line:90%
It says 10.

00:00:36.040 --> 00:00:36.540 align:middle line:90%
100.

00:00:36.540 --> 00:00:39.370 align:middle line:90%
13.

00:00:39.370 --> 00:00:43.690 align:middle line:90%
And let's run an Nmap on event.

00:00:43.690 --> 00:00:44.725 align:middle line:90%
Zero set at 24.

00:00:44.725 --> 00:00:48.870 align:middle line:90%


00:00:48.870 --> 00:00:51.840 align:middle line:90%
And we're 140.

00:00:51.840 --> 00:00:55.060 align:middle line:90%
I know, it's a strange number.

00:00:55.060 --> 00:00:56.620 align:middle line:84%
Well, it's just
not a round number.

00:00:56.620 --> 00:00:57.790 align:middle line:90%
It's not one, two or three.

00:00:57.790 --> 00:01:16.770 align:middle line:90%


00:01:16.770 --> 00:01:19.070 align:middle line:90%
We have our results back.

00:01:19.070 --> 00:01:22.680 align:middle line:90%
.1 is going to be our--

00:01:22.680 --> 00:01:27.510 align:middle line:84%
looks like our webserver.
.36 has Telnet open,

00:01:27.510 --> 00:01:33.750 align:middle line:84%
and .37 looks to be a machine
that isn't hosting anything.

00:01:33.750 --> 00:01:37.140 align:middle line:90%
And we're .40 or .140.

00:01:37.140 --> 00:01:38.360 align:middle line:90%
All right.

00:01:38.360 --> 00:01:39.960 align:middle line:90%
Now that's kind of fun.

00:01:39.960 --> 00:01:42.120 align:middle line:90%
Let's check our Wireshark.

00:01:42.120 --> 00:01:45.608 align:middle line:90%


00:01:45.608 --> 00:01:47.650 align:middle line:84%
Let's see what's going on
in this network, right?

00:01:47.650 --> 00:01:54.250 align:middle line:90%


00:01:54.250 --> 00:01:59.060 align:middle line:84%
And to match ETH1 is what
we want to be searching on.

00:01:59.060 --> 00:01:59.780 align:middle line:90%
And let's listen.

00:01:59.780 --> 00:02:03.230 align:middle line:90%


00:02:03.230 --> 00:02:05.153 align:middle line:90%
It's not really much happening.

00:02:05.153 --> 00:02:08.860 align:middle line:90%


00:02:08.860 --> 00:02:12.650 align:middle line:84%
Because we're not
talking to anyone.

00:02:12.650 --> 00:02:16.737 align:middle line:84%
Let's just make
sure things work.

00:02:16.737 --> 00:02:17.945 align:middle line:90%
Let's ping one of these guys.

00:02:17.945 --> 00:02:24.040 align:middle line:90%


00:02:24.040 --> 00:02:24.610 align:middle line:90%
Bam.

00:02:24.610 --> 00:02:25.150 align:middle line:90%
OK.

00:02:25.150 --> 00:02:28.150 align:middle line:90%
I see ping is going on.

00:02:28.150 --> 00:02:38.050 align:middle line:84%
Well, what we want to do
is, there is Telnet open.

00:02:38.050 --> 00:02:42.140 align:middle line:84%
We aren't seeing any traffic
between other machines.

00:02:42.140 --> 00:02:46.090 align:middle line:84%
So let's-- I don't know, let's
pretend to be someone else

00:02:46.090 --> 00:02:48.790 align:middle line:84%
and see if we can intercept
traffic that's not intended

00:02:48.790 --> 00:02:49.300 align:middle line:90%
for us.

00:02:49.300 --> 00:02:52.340 align:middle line:90%


00:02:52.340 --> 00:02:58.230 align:middle line:84%
So the way we go
about that is we're

00:02:58.230 --> 00:03:05.020 align:middle line:84%
going to take, echo
our standard in

00:03:05.020 --> 00:03:07.330 align:middle line:84%
and then we're going to
send that to IP forward.

00:03:07.330 --> 00:03:10.180 align:middle line:90%


00:03:10.180 --> 00:03:12.000 align:middle line:90%
And we're doing that because--

00:03:12.000 --> 00:03:15.920 align:middle line:90%


00:03:15.920 --> 00:03:18.360 align:middle line:90%
oh, we already have something.

00:03:18.360 --> 00:03:19.115 align:middle line:90%
All right.

00:03:19.115 --> 00:03:23.940 align:middle line:90%


00:03:23.940 --> 00:03:26.870 align:middle line:84%
Let's really to do
this ARP spoofing.

00:03:26.870 --> 00:03:31.270 align:middle line:84%
And you can see a whole
bunch of traffic out here.

00:03:31.270 --> 00:03:34.630 align:middle line:84%
Where we are sending
our ARP information out.

00:03:34.630 --> 00:03:42.080 align:middle line:90%


00:03:42.080 --> 00:03:44.525 align:middle line:90%
Oh, you see Telnet traffic.

00:03:44.525 --> 00:03:48.550 align:middle line:90%


00:03:48.550 --> 00:03:50.290 align:middle line:84%
That might be what
we're looking for.

00:03:50.290 --> 00:03:51.780 align:middle line:90%
Let's stop this capture.

00:03:51.780 --> 00:03:54.655 align:middle line:90%


00:03:54.655 --> 00:03:56.320 align:middle line:84%
We're also going
to stop the scan.

00:03:56.320 --> 00:03:58.970 align:middle line:90%


00:03:58.970 --> 00:04:01.070 align:middle line:84%
Cleaning up and
reopening the target.

00:04:01.070 --> 00:04:02.090 align:middle line:90%
That's good.

00:04:02.090 --> 00:04:04.070 align:middle line:90%
We'll let him do his cleanup.

00:04:04.070 --> 00:04:05.270 align:middle line:90%
Saw something in here.

00:04:05.270 --> 00:04:08.597 align:middle line:90%
Telnet traffic.

00:04:08.597 --> 00:04:09.680 align:middle line:90%
Who is that intended from?

00:04:09.680 --> 00:04:11.780 align:middle line:90%
From 36 to 37.

00:04:11.780 --> 00:04:13.762 align:middle line:90%
So it wasn't going to us.

00:04:13.762 --> 00:04:15.845 align:middle line:84%
This traffic wasn't intended
for us, we're about .

00:04:15.845 --> 00:04:17.180 align:middle line:90%
140, right?

00:04:17.180 --> 00:04:19.470 align:middle line:90%
This one's going from 36 to 37.

00:04:19.470 --> 00:04:22.160 align:middle line:84%
And if we were
plugged into a switch,

00:04:22.160 --> 00:04:26.572 align:middle line:84%
if we were gathering data
from, basically from a switch,

00:04:26.572 --> 00:04:27.780 align:middle line:90%
it's the best way to do that.

00:04:27.780 --> 00:04:30.980 align:middle line:84%
Or if you had a line
in between switches

00:04:30.980 --> 00:04:33.440 align:middle line:84%
and you gathered all the traffic
even if it wasn't intended

00:04:33.440 --> 00:04:37.220 align:middle line:90%
for us, that might work.

00:04:37.220 --> 00:04:44.150 align:middle line:84%
But by our ARP spoofing,
we told 36 that we were 37.

00:04:44.150 --> 00:04:46.580 align:middle line:84%
And said, hey, send
that over here.

00:04:46.580 --> 00:04:48.230 align:middle line:84%
And then we were
able to listen to it.

00:04:48.230 --> 00:04:52.500 align:middle line:84%
And let's dig in and see
what that looks like.

00:04:52.500 --> 00:04:55.610 align:middle line:90%
So it is Telnet.

00:04:55.610 --> 00:04:58.400 align:middle line:90%
Lots of Telnet data.

00:04:58.400 --> 00:05:02.390 align:middle line:84%
Let's follow the stream
and see what's in here.

00:05:02.390 --> 00:05:04.190 align:middle line:90%
Oh, hey, we have a log in.

00:05:04.190 --> 00:05:09.590 align:middle line:84%
Only log in with admin
and my secret pass.

00:05:09.590 --> 00:05:13.280 align:middle line:90%
Let's copy that code.

00:05:13.280 --> 00:05:16.820 align:middle line:90%
And let's pull this back up.

00:05:16.820 --> 00:05:21.380 align:middle line:84%
It was going from which
machine to which machine?

00:05:21.380 --> 00:05:24.880 align:middle line:90%


00:05:24.880 --> 00:05:26.185 align:middle line:90%
From 36 to 37.

00:05:26.185 --> 00:05:30.670 align:middle line:90%


00:05:30.670 --> 00:05:32.600 align:middle line:84%
It would be way too
much to go back.

00:05:32.600 --> 00:05:34.120 align:middle line:90%
Not that-- not that far.

00:05:34.120 --> 00:05:38.870 align:middle line:90%


00:05:38.870 --> 00:05:42.890 align:middle line:84%
Yeah, it is 36 that
has Telnet open.

00:05:42.890 --> 00:05:45.320 align:middle line:90%
So let's Telnet to 36.

00:05:45.320 --> 00:05:52.470 align:middle line:90%


00:05:52.470 --> 00:06:05.500 align:middle line:90%
In .100 .13 .36.

00:06:05.500 --> 00:06:07.105 align:middle line:90%
INE log in.

00:06:07.105 --> 00:06:16.556 align:middle line:84%
And we saw that the username
is admin and the password.

00:06:16.556 --> 00:06:18.950 align:middle line:90%
So that copies.

00:06:18.950 --> 00:06:23.720 align:middle line:90%
Hey, it worked.

00:06:23.720 --> 00:06:28.130 align:middle line:84%
Copied in that my secret
pass from up here.

00:06:28.130 --> 00:06:30.160 align:middle line:90%
Use the keyboard command.

00:06:30.160 --> 00:06:33.530 align:middle line:84%
And it says welcome to
Ubuntu, which is something

00:06:33.530 --> 00:06:35.390 align:middle line:90%
since we were on Kali before.

00:06:35.390 --> 00:06:37.520 align:middle line:84%
And now you can see
we are now Telneted

00:06:37.520 --> 00:06:42.330 align:middle line:90%
into this other server.

00:06:42.330 --> 00:06:44.000 align:middle line:84%
That's one of the
dangers of Telnet.

00:06:44.000 --> 00:06:51.710 align:middle line:84%
Is it's not secured or
it's not encrypted in root.

00:06:51.710 --> 00:06:56.930 align:middle line:84%
So we were able to ARP spoof
and capture that traffic

00:06:56.930 --> 00:06:57.800 align:middle line:90%
and read it.

00:06:57.800 --> 00:06:59.180 align:middle line:90%
And then utilize it.

00:06:59.180 --> 00:07:03.950 align:middle line:84%
Since log in is not
encrypted, we grabbed it.

00:07:03.950 --> 00:07:07.530 align:middle line:84%
And we were able to log in
on the machine on our own.

00:07:07.530 --> 00:07:08.480 align:middle line:90%
It's kind of nice.

00:07:08.480 --> 00:07:11.210 align:middle line:84%
We could cover our own
tracks and maybe use

00:07:11.210 --> 00:07:14.930 align:middle line:84%
this machine to SSH
back to ourselves

00:07:14.930 --> 00:07:16.790 align:middle line:90%
through this Telnet session.

00:07:16.790 --> 00:07:21.690 align:middle line:84%
And then we might
have access that way.

00:07:21.690 --> 00:07:24.710 align:middle line:84%
And have then whatever
we're doing from there

00:07:24.710 --> 00:07:32.290 align:middle line:84%
become encrypted and harder
to look at forensically.

00:07:32.290 --> 00:07:39.840 align:middle line:84%
But this is just base level
man in the middle spoofing,

00:07:39.840 --> 00:07:42.600 align:middle line:84%
listening, and then
utilizing what we found.

00:07:42.600 --> 00:07:48.720 align:middle line:84%
Now let's, in the next
couple of labs, let's dig in

00:07:48.720 --> 00:07:53.880 align:middle line:84%
and do something a little more
sophisticated if you will.

00:07:53.880 --> 00:07:57.060 align:middle line:84%
Let's look at Wi-Fi and
see what that looks like

00:07:57.060 --> 00:07:59.780 align:middle line:84%
and what we might
be able to do there.

00:07:59.780 --> 00:08:01.000 align:middle line:90%