WEBVTT

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


00:00:03.700 --> 00:00:06.220 align:middle line:84%
This is the first of our
challenges in this section.

00:00:06.220 --> 00:00:09.257 align:middle line:90%
I'm Josh Mason, your instructor.

00:00:09.257 --> 00:00:10.090 align:middle line:90%
Let's get to the VN.

00:00:10.090 --> 00:00:13.530 align:middle line:90%


00:00:13.530 --> 00:00:15.690 align:middle line:90%
We have a console here.

00:00:15.690 --> 00:00:23.160 align:middle line:84%
And we see that our IP
address is this 192.148.40.2.

00:00:23.160 --> 00:00:32.570 align:middle line:84%
So we're going to be
looking for 192.148.40.3

00:00:32.570 --> 00:00:36.830 align:middle line:84%
from the instructions
to cider 24.

00:00:36.830 --> 00:00:39.200 align:middle line:84%
So I know-- well,
it also tells us.

00:00:39.200 --> 00:00:40.916 align:middle line:90%
The gateway is dot 1.

00:00:40.916 --> 00:00:45.330 align:middle line:84%
So dot 2 is us and
dot 3 is the target.

00:00:45.330 --> 00:00:46.340 align:middle line:90%
Let's ping it real fast.

00:00:46.340 --> 00:00:48.950 align:middle line:90%


00:00:48.950 --> 00:00:51.095 align:middle line:84%
And it is up, so
that is helpful.

00:00:51.095 --> 00:00:54.630 align:middle line:90%


00:00:54.630 --> 00:01:00.090 align:middle line:84%
We'll just run an nmap scan and
see if there are ports open.

00:01:00.090 --> 00:01:01.800 align:middle line:90%
Nothing showing.

00:01:01.800 --> 00:01:04.980 align:middle line:90%
We'll do a tack, p, tack.

00:01:04.980 --> 00:01:10.200 align:middle line:84%
Check the first-- or not the
first, but top 1,000 ports.

00:01:10.200 --> 00:01:12.100 align:middle line:90%
It gets a misconception.

00:01:12.100 --> 00:01:15.540 align:middle line:84%
It checks the top 1,000 ports,
not the first 1,000 ports.

00:01:15.540 --> 00:01:18.750 align:middle line:84%
A tack, p, tack is going
to check all of the ports.

00:01:18.750 --> 00:01:23.540 align:middle line:90%


00:01:23.540 --> 00:01:29.000 align:middle line:84%
So we see there were 65,532
closed ports and these three

00:01:29.000 --> 00:01:31.400 align:middle line:90%
open ports.

00:01:31.400 --> 00:01:33.740 align:middle line:90%
This one's saying nim-won so--

00:01:33.740 --> 00:01:37.120 align:middle line:90%
wan, whatever.

00:01:37.120 --> 00:01:38.500 align:middle line:90%
It's guessing.

00:01:38.500 --> 00:01:40.190 align:middle line:90%
We haven't done a service scan.

00:01:40.190 --> 00:01:43.720 align:middle line:84%
So what we can do now
that we know these ports--

00:01:43.720 --> 00:01:55.650 align:middle line:90%
6421.41288 and 55413.

00:01:55.650 --> 00:01:57.420 align:middle line:84%
Let's do a service
enumeration on them.

00:01:57.420 --> 00:02:03.140 align:middle line:90%


00:02:03.140 --> 00:02:07.520 align:middle line:84%
That went pretty fast because
we targeted just those three.

00:02:07.520 --> 00:02:09.470 align:middle line:90%
And nice and straightforward.

00:02:09.470 --> 00:02:14.030 align:middle line:90%
6421 is our MongoDB.

00:02:14.030 --> 00:02:17.270 align:middle line:90%
41288 is the memecached.

00:02:17.270 --> 00:02:24.680 align:middle line:90%
And 55413 is the FTP.

00:02:24.680 --> 00:02:28.550 align:middle line:90%
That was fairly straightforward.

00:02:28.550 --> 00:02:31.600 align:middle line:84%
Did require us to
use tack, p, tack.

00:02:31.600 --> 00:02:33.000 align:middle line:90%