WEBVTT

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


00:00:03.620 --> 00:00:06.350 align:middle line:84%
This is our third and final
challenge in this section.

00:00:06.350 --> 00:00:09.020 align:middle line:84%
I'm Josh Mason, and
I'll be walking you

00:00:09.020 --> 00:00:15.480 align:middle line:90%
through this challenge.

00:00:15.480 --> 00:00:18.990 align:middle line:90%
Will grab our IP address.

00:00:18.990 --> 00:00:27.630 align:middle line:84%
You gave us the one
192.57.232 and it'll

00:00:27.630 --> 00:00:30.410 align:middle line:90%
be dot-3 for all of our work.

00:00:30.410 --> 00:00:33.480 align:middle line:90%
So just ping it real fast.

00:00:33.480 --> 00:00:37.330 align:middle line:90%


00:00:37.330 --> 00:00:38.495 align:middle line:90%
And It is there.

00:00:38.495 --> 00:00:44.400 align:middle line:90%


00:00:44.400 --> 00:00:45.230 align:middle line:90%
Let's run that.

00:00:45.230 --> 00:00:50.740 align:middle line:90%


00:00:50.740 --> 00:00:54.400 align:middle line:84%
I'm going to put
in a T4 for speed

00:00:54.400 --> 00:00:58.570 align:middle line:90%
and see if we get anything.

00:00:58.570 --> 00:01:00.770 align:middle line:90%
And it's scanned.

00:01:00.770 --> 00:01:01.270 align:middle line:90%
Top out.

00:01:01.270 --> 00:01:03.670 align:middle line:84%
That was really fast
and found nothing.

00:01:03.670 --> 00:01:07.630 align:middle line:84%
We'll run it with -p- to
run all the TSP ports.

00:01:07.630 --> 00:01:11.010 align:middle line:90%


00:01:11.010 --> 00:01:15.320 align:middle line:84%
And that came back
really fast with nothing.

00:01:15.320 --> 00:01:18.530 align:middle line:90%
So then we go with the less fun.

00:01:18.530 --> 00:01:20.540 align:middle line:90%
-su.

00:01:20.540 --> 00:01:21.830 align:middle line:90%
And this might take a while.

00:01:21.830 --> 00:01:25.730 align:middle line:90%


00:01:25.730 --> 00:01:28.100 align:middle line:90%
That took a while.

00:01:28.100 --> 00:01:34.210 align:middle line:84%
It says it scanned
for 1,032 seconds.

00:01:34.210 --> 00:01:36.930 align:middle line:90%
So it's close to--

00:01:36.930 --> 00:01:39.640 align:middle line:90%
it was a while.

00:01:39.640 --> 00:01:45.090 align:middle line:84%
Anyways, we see that we have
port 161 open with SNMP.

00:01:45.090 --> 00:01:50.820 align:middle line:84%
Now, I don't know
much about that SNMP.

00:01:50.820 --> 00:01:53.800 align:middle line:84%
It is just a best guess
based on that port.

00:01:53.800 --> 00:01:59.100 align:middle line:84%
So let's scan 161 and do
an aggressive scan, just

00:01:59.100 --> 00:02:00.367 align:middle line:90%
on that single port.

00:02:00.367 --> 00:02:01.575 align:middle line:90%
This should go a lot quicker.

00:02:01.575 --> 00:02:07.080 align:middle line:90%


00:02:07.080 --> 00:02:08.190 align:middle line:90%
And it did.

00:02:08.190 --> 00:02:09.990 align:middle line:84%
It came back with
some useful stuff.

00:02:09.990 --> 00:02:16.970 align:middle line:90%


00:02:16.970 --> 00:02:17.570 align:middle line:90%
All right.

00:02:17.570 --> 00:02:25.140 align:middle line:84%
So it's running SNMP Version
1 Server and that SNMP.

00:02:25.140 --> 00:02:25.860 align:middle line:90%
Good to know.

00:02:25.860 --> 00:02:26.910 align:middle line:90%
Good to know.

00:02:26.910 --> 00:02:30.830 align:middle line:84%
There's some things
that it is asking.

00:02:30.830 --> 00:02:35.240 align:middle line:84%
What interface do we have
that is publicly facing?

00:02:35.240 --> 00:02:39.710 align:middle line:84%
The only two interfaces are
this loopback, LO, and eth0.

00:02:39.710 --> 00:02:44.060 align:middle line:84%
So eth0 with the
192, it's going to be

00:02:44.060 --> 00:02:49.520 align:middle line:90%
the public-facing interface.

00:02:49.520 --> 00:02:50.420 align:middle line:90%
So eth0.

00:02:50.420 --> 00:02:53.610 align:middle line:90%


00:02:53.610 --> 00:03:00.270 align:middle line:84%
Then, we're looking for
some SSH keys for David.

00:03:00.270 --> 00:03:04.170 align:middle line:90%


00:03:04.170 --> 00:03:06.990 align:middle line:90%
And this ran some scripts.

00:03:06.990 --> 00:03:09.660 align:middle line:90%
It did some enumeration for us.

00:03:09.660 --> 00:03:15.540 align:middle line:84%
That aggressive scan with
the -sc and -sv included

00:03:15.540 --> 00:03:18.700 align:middle line:84%
gets you a lot of
good information.

00:03:18.700 --> 00:03:23.850 align:middle line:84%
So we see SSH utilizes
tack-i, which will take a key.

00:03:23.850 --> 00:03:27.150 align:middle line:84%
So the key is held
at opt/david_key.

00:03:27.150 --> 00:03:30.180 align:middle line:90%


00:03:30.180 --> 00:03:30.930 align:middle line:90%
It's good to know.

00:03:30.930 --> 00:03:35.190 align:middle line:90%


00:03:35.190 --> 00:03:39.870 align:middle line:84%
And then, there is a loopback
report that we're listening on.

00:03:39.870 --> 00:03:43.730 align:middle line:90%


00:03:43.730 --> 00:03:47.795 align:middle line:84%
And you can see we're
listening on port 22 for TCP.

00:03:47.795 --> 00:03:50.540 align:middle line:90%


00:03:50.540 --> 00:03:57.370 align:middle line:84%
And then also
listening on this 1313.

00:03:57.370 --> 00:04:00.460 align:middle line:90%
This is really helpful.

00:04:00.460 --> 00:04:07.090 align:middle line:84%
And we could try to connect, if
we own this machine, to figure

00:04:07.090 --> 00:04:10.870 align:middle line:90%
out what we were running there.

00:04:10.870 --> 00:04:14.440 align:middle line:90%
But it's only on loopback.

00:04:14.440 --> 00:04:16.599 align:middle line:84%
So we're not going to
see it, I don't think.

00:04:16.599 --> 00:04:21.175 align:middle line:90%


00:04:21.175 --> 00:04:22.300 align:middle line:90%
But that was the challenge.

00:04:22.300 --> 00:04:31.250 align:middle line:84%
It was really to have
you run a UDP scan.

00:04:31.250 --> 00:04:34.360 align:middle line:84%
And we found what
we were looking for.

00:04:34.360 --> 00:04:38.000 align:middle line:90%