WEBVTT

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


00:00:03.710 --> 00:00:06.320 align:middle line:84%
Welcome to the second
challenge in our series.

00:00:06.320 --> 00:00:08.060 align:middle line:84%
I'm Josh Mason, your
instructor again.

00:00:08.060 --> 00:00:10.670 align:middle line:90%


00:00:10.670 --> 00:00:14.540 align:middle line:90%
We have a console.

00:00:14.540 --> 00:00:25.850 align:middle line:84%
And we find our IP address
is going to be 192.206.172.2.

00:00:25.850 --> 00:00:33.480 align:middle line:84%
And they tell us dot 3 is our
target on this little network.

00:00:33.480 --> 00:00:35.760 align:middle line:90%
Dot 1 is our gateway.

00:00:35.760 --> 00:00:37.760 align:middle line:90%
It's pretty straightforward.

00:00:37.760 --> 00:00:39.120 align:middle line:90%
Let's make sure it's there.

00:00:39.120 --> 00:00:41.100 align:middle line:90%
It's responding.

00:00:41.100 --> 00:00:43.090 align:middle line:90%
Good.

00:00:43.090 --> 00:00:45.370 align:middle line:90%
Let's run our in-depth scans.

00:00:45.370 --> 00:00:48.940 align:middle line:84%
They tell us that the
system administrator has

00:00:48.940 --> 00:00:56.020 align:middle line:84%
moved all of the services
to ports 1 through 250,

00:00:56.020 --> 00:00:59.080 align:middle line:84%
but they're not in
their standard location.

00:00:59.080 --> 00:01:01.960 align:middle line:84%
Their known location,
their default location,

00:01:01.960 --> 00:01:05.630 align:middle line:90%
that's a better term for it.

00:01:05.630 --> 00:01:07.660 align:middle line:84%
So let's see if there's
anything out there.

00:01:07.660 --> 00:01:12.670 align:middle line:90%
Oh, you can see 177.

00:01:12.670 --> 00:01:19.160 align:middle line:84%
Let's run an
aggressive scan on 177.

00:01:19.160 --> 00:01:22.670 align:middle line:84%
And the aggressive scan is
going to do the operating system

00:01:22.670 --> 00:01:23.750 align:middle line:90%
fingerprinting.

00:01:23.750 --> 00:01:28.100 align:middle line:84%
It's going to look for
service information.

00:01:28.100 --> 00:01:30.710 align:middle line:84%
It's going to connect
and try to grab a banner.

00:01:30.710 --> 00:01:33.320 align:middle line:84%
It's also going to run
the default scripts.

00:01:33.320 --> 00:01:37.100 align:middle line:84%
And it's going to do a
traceroute, which should just

00:01:37.100 --> 00:01:38.330 align:middle line:90%
be one hop at the gateway.

00:01:38.330 --> 00:01:47.510 align:middle line:90%


00:01:47.510 --> 00:01:49.100 align:middle line:90%
And we have our results back.

00:01:49.100 --> 00:01:55.520 align:middle line:84%
We see that port 177
has the the ISC BIND.

00:01:55.520 --> 00:01:59.240 align:middle line:84%
We're still looking for
our TFTP and our SNMP.

00:01:59.240 --> 00:02:05.630 align:middle line:84%
And I see BIND is a DNS
service, so I expect

00:02:05.630 --> 00:02:08.039 align:middle line:90%
there to be a UDP as well.

00:02:08.039 --> 00:02:09.900 align:middle line:90%
So we'll look for that.

00:02:09.900 --> 00:02:15.050 align:middle line:84%
So let's run our same scan
again with the tag sU.

00:02:15.050 --> 00:02:18.350 align:middle line:84%
Because we know those
three are going to be here.

00:02:18.350 --> 00:02:26.030 align:middle line:84%
And they didn't show up in
TCP, so we'll check UDP.

00:02:26.030 --> 00:02:27.660 align:middle line:90%
And this scan can take a while.

00:02:27.660 --> 00:02:32.090 align:middle line:84%
So there's a good chance
the video cuts and we end up

00:02:32.090 --> 00:02:33.725 align:middle line:90%
at the results.

00:02:33.725 --> 00:02:43.140 align:middle line:90%


00:02:43.140 --> 00:02:46.100 align:middle line:84%
All right, so we got
our results back.

00:02:46.100 --> 00:02:53.510 align:middle line:84%
We've got three UDP
ports, 134, 177, and 234.

00:02:53.510 --> 00:03:02.260 align:middle line:84%
So we will hone in on
those three results

00:03:02.260 --> 00:03:10.910 align:middle line:84%
and do a service scan,
only that U as well.

00:03:10.910 --> 00:03:15.580 align:middle line:84%
So it does the UDP ports,
looking for that service.

00:03:15.580 --> 00:03:17.800 align:middle line:84%
Making sure I'm not
missing anything

00:03:17.800 --> 00:03:21.400 align:middle line:84%
because we don't know
which one's which.

00:03:21.400 --> 00:03:25.360 align:middle line:90%
I assume 177 is, again the BIND.

00:03:25.360 --> 00:03:28.900 align:middle line:90%
But we should test.

00:03:28.900 --> 00:03:30.310 align:middle line:90%
So we'll scan again.

00:03:30.310 --> 00:03:33.690 align:middle line:84%
Since we're only scanning
those three ports,

00:03:33.690 --> 00:03:35.065 align:middle line:84%
it should go a
little bit faster.

00:03:35.065 --> 00:03:43.410 align:middle line:90%


00:03:43.410 --> 00:03:46.380 align:middle line:90%
And we got our results back.

00:03:46.380 --> 00:03:51.330 align:middle line:84%
It looks like 134 is
showing open and filtered.

00:03:51.330 --> 00:03:54.900 align:middle line:84%
We're not getting great
info back from that.

00:03:54.900 --> 00:03:56.730 align:middle line:90%
We'll dive into that in a sec.

00:03:56.730 --> 00:04:00.900 align:middle line:84%
But 177 is showing
that ISC BIND.

00:04:00.900 --> 00:04:05.910 align:middle line:90%
And 234 getting the SNMP.

00:04:05.910 --> 00:04:10.020 align:middle line:84%
So we could assume
that that's the TFTP,

00:04:10.020 --> 00:04:12.945 align:middle line:90%
but I want to do one better.

00:04:12.945 --> 00:04:18.220 align:middle line:90%


00:04:18.220 --> 00:04:19.464 align:middle line:90%
Why is it having problems?

00:04:19.464 --> 00:04:22.029 align:middle line:90%


00:04:22.029 --> 00:04:25.240 align:middle line:90%
Let's dial in on that one.

00:04:25.240 --> 00:04:30.150 align:middle line:90%
And let's run some scripts.

00:04:30.150 --> 00:04:37.460 align:middle line:90%


00:04:37.460 --> 00:04:38.690 align:middle line:90%
It's like adding a tag SC--

00:04:38.690 --> 00:04:57.260 align:middle line:90%


00:04:57.260 --> 00:05:03.730 align:middle line:84%
in Rome, the discovery script
or the discovery set of scripts.

00:05:03.730 --> 00:05:08.230 align:middle line:90%


00:05:08.230 --> 00:05:11.230 align:middle line:84%
See if there's something
more that we're not getting.

00:05:11.230 --> 00:05:19.540 align:middle line:90%


00:05:19.540 --> 00:05:23.260 align:middle line:84%
OK, even with the discovery
scan result coming back,

00:05:23.260 --> 00:05:31.915 align:middle line:84%
we still do you not have
it showing us the service.

00:05:31.915 --> 00:05:34.552 align:middle line:90%


00:05:34.552 --> 00:05:35.510 align:middle line:90%
So let's try something.

00:05:35.510 --> 00:05:54.600 align:middle line:90%
We'll just do TFTP on port 134.

00:05:54.600 --> 00:05:55.920 align:middle line:90%
And it says we're connected.

00:05:55.920 --> 00:06:00.000 align:middle line:90%


00:06:00.000 --> 00:06:01.915 align:middle line:90%
OK.

00:06:01.915 --> 00:06:02.790 align:middle line:90%
Let's try that again.

00:06:02.790 --> 00:06:09.400 align:middle line:90%


00:06:09.400 --> 00:06:17.070 align:middle line:84%
Based off that usage right
there, it didn't like my tag p.

00:06:17.070 --> 00:06:20.050 align:middle line:84%
It just wanted
hostname and then port.

00:06:20.050 --> 00:06:22.930 align:middle line:84%
And so we did hostname and
then port with that status.

00:06:22.930 --> 00:06:24.510 align:middle line:90%
And it says it's there.

00:06:24.510 --> 00:06:28.560 align:middle line:84%
With that, I will
definitively say that port 134

00:06:28.560 --> 00:06:34.010 align:middle line:90%
is hosting the TFTP server.

00:06:34.010 --> 00:06:37.000 align:middle line:90%