WEBVTT

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


00:00:03.360 --> 00:00:06.720 align:middle line:90%
[MUSIC LOGO]

00:00:06.720 --> 00:00:10.580 align:middle line:90%


00:00:10.580 --> 00:00:13.100 align:middle line:84%
The next protocol we'll
be looking at is SSH.

00:00:13.100 --> 00:00:15.150 align:middle line:90%
It is very common.

00:00:15.150 --> 00:00:16.910 align:middle line:84%
It's used for remote
administration.

00:00:16.910 --> 00:00:19.760 align:middle line:84%
It gives you a
secure shell, which

00:00:19.760 --> 00:00:24.380 align:middle line:84%
is what SSH stands for, and
allows you to then interact

00:00:24.380 --> 00:00:28.295 align:middle line:84%
with a remote machine
over an encrypted channel.

00:00:28.295 --> 00:00:30.170 align:middle line:84%
So let's take a look at
what that looks like.

00:00:30.170 --> 00:00:34.880 align:middle line:90%


00:00:34.880 --> 00:00:37.640 align:middle line:90%
We have our IP address.

00:00:37.640 --> 00:00:42.110 align:middle line:90%
We are 192.244.143.2.

00:00:42.110 --> 00:00:47.420 align:middle line:84%
So our victim is going to
be the .3 version event.

00:00:47.420 --> 00:00:51.120 align:middle line:90%


00:00:51.120 --> 00:00:54.310 align:middle line:90%
And it is up and running.

00:00:54.310 --> 00:00:56.340 align:middle line:84%
So let's do a quick
scan with nmap.

00:00:56.340 --> 00:00:59.730 align:middle line:90%


00:00:59.730 --> 00:01:01.920 align:middle line:90%
And we see that port 22 is open.

00:01:01.920 --> 00:01:04.505 align:middle line:90%


00:01:04.505 --> 00:01:07.690 align:middle line:90%
And it says it's running ssh.

00:01:07.690 --> 00:01:12.610 align:middle line:84%
Let's do a quick service
scan, operating system scan.

00:01:12.610 --> 00:01:27.890 align:middle line:90%


00:01:27.890 --> 00:01:28.910 align:middle line:90%
And it came back.

00:01:28.910 --> 00:01:34.250 align:middle line:84%
It's running OpenSSH
7.2 for Ubuntu.

00:01:34.250 --> 00:01:36.890 align:middle line:90%
Using Ubuntu 2.6.

00:01:36.890 --> 00:01:38.720 align:middle line:90%
It says Ubuntu Linux.

00:01:38.720 --> 00:01:47.060 align:middle line:84%
And the fingerprint also comes
back, well, with a fingerprint.

00:01:47.060 --> 00:01:48.573 align:middle line:90%
Doesn't really mean much to me.

00:01:48.573 --> 00:01:49.865 align:middle line:90%
So there's no exact OS matches.

00:01:49.865 --> 00:01:52.370 align:middle line:90%


00:01:52.370 --> 00:01:56.160 align:middle line:84%
But the software is the
Ubuntu version of OpenSSH.

00:01:56.160 --> 00:01:58.520 align:middle line:90%
So that's the dead giveaway.

00:01:58.520 --> 00:02:03.770 align:middle line:84%
How this works is normally
do ssh and then a user root.

00:02:03.770 --> 00:02:06.890 align:middle line:84%
It's almost on
every Linux machine.

00:02:06.890 --> 00:02:09.230 align:middle line:90%
Root @ our IP address.

00:02:09.230 --> 00:02:13.410 align:middle line:90%


00:02:13.410 --> 00:02:17.460 align:middle line:84%
And it says, hey, authentication
can't be established.

00:02:17.460 --> 00:02:22.380 align:middle line:84%
Here is the
fingerprint, the SHA256.

00:02:22.380 --> 00:02:24.960 align:middle line:84%
Are you sure you want
to continue connecting?

00:02:24.960 --> 00:02:26.760 align:middle line:84%
Normally, we would
check that, make sure

00:02:26.760 --> 00:02:29.580 align:middle line:84%
that it's what we
expect for that machine.

00:02:29.580 --> 00:02:31.260 align:middle line:90%
We'll say yes.

00:02:31.260 --> 00:02:32.220 align:middle line:90%
Have to type out yes.

00:02:32.220 --> 00:02:36.590 align:middle line:90%


00:02:36.590 --> 00:02:41.000 align:middle line:84%
It says, welcome to attack
defense ssh recon lab!!

00:02:41.000 --> 00:02:42.710 align:middle line:90%
That is the banner.

00:02:42.710 --> 00:02:44.660 align:middle line:84%
We haven't even
authenticated, and it already

00:02:44.660 --> 00:02:53.590 align:middle line:84%
told us that it is
what the name of it is.

00:02:53.590 --> 00:02:56.680 align:middle line:84%
Now, it's asking
for root's password.

00:02:56.680 --> 00:03:02.900 align:middle line:90%
Try, like, password123.

00:03:02.900 --> 00:03:07.490 align:middle line:84%
And you get three chances
usually for a password.

00:03:07.490 --> 00:03:08.750 align:middle line:90%
We'll just exit out of that.

00:03:08.750 --> 00:03:14.300 align:middle line:90%


00:03:14.300 --> 00:03:16.310 align:middle line:84%
Now that we've seen
what service is running,

00:03:16.310 --> 00:03:20.240 align:middle line:84%
and we've kind of
connected to it-- oh.

00:03:20.240 --> 00:03:23.030 align:middle line:90%
Let's Netcat to it.

00:03:23.030 --> 00:03:27.380 align:middle line:84%
Rather than using the
ssh tool, we will just

00:03:27.380 --> 00:03:37.650 align:middle line:84%
utilize Netcat, which will
connect, and it says 22.

00:03:37.650 --> 00:03:39.690 align:middle line:90%
Connect to port 22.

00:03:39.690 --> 00:03:41.460 align:middle line:84%
And that gives us
this banner, which

00:03:41.460 --> 00:03:44.490 align:middle line:84%
is how it did the
fingerprint scan before.

00:03:44.490 --> 00:03:50.750 align:middle line:90%


00:03:50.750 --> 00:03:53.900 align:middle line:84%
And it doesn't give us much
more than that with Netcat.

00:03:53.900 --> 00:03:55.250 align:middle line:90%
It's a protocol mismatch.

00:03:55.250 --> 00:03:57.920 align:middle line:84%
But it still gave
us the banner, which

00:03:57.920 --> 00:03:59.993 align:middle line:84%
was useful for
enumeration, which

00:03:59.993 --> 00:04:01.160 align:middle line:90%
is what we're doing, really.

00:04:01.160 --> 00:04:07.092 align:middle line:90%


00:04:07.092 --> 00:04:08.800 align:middle line:84%
Now that we've seen
the banner, and we've

00:04:08.800 --> 00:04:17.160 align:middle line:84%
seen the welcome message,
let's do some more enumeration

00:04:17.160 --> 00:04:20.100 align:middle line:90%
on the machine, port 22.

00:04:20.100 --> 00:04:32.220 align:middle line:84%
We're going to run the script,
ssh2-enum-algos to enumerate

00:04:32.220 --> 00:04:33.540 align:middle line:90%
all the algorithms.

00:04:33.540 --> 00:04:38.398 align:middle line:90%


00:04:38.398 --> 00:04:39.190 align:middle line:90%
And this is useful.

00:04:39.190 --> 00:04:40.810 align:middle line:84%
It shows us all
the algorithms that

00:04:40.810 --> 00:04:43.855 align:middle line:90%
can be used to create that key.

00:04:43.855 --> 00:04:47.623 align:middle line:90%


00:04:47.623 --> 00:04:49.290 align:middle line:84%
We're going to want
to write these down.

00:04:49.290 --> 00:04:51.900 align:middle line:84%
And if we need them
later, we have them.

00:04:51.900 --> 00:04:56.630 align:middle line:90%


00:04:56.630 --> 00:05:00.980 align:middle line:84%
What's really helpful
is we want that rsa key.

00:05:00.980 --> 00:05:08.930 align:middle line:90%


00:05:08.930 --> 00:05:15.440 align:middle line:84%
It's the primary way
that ssh actually

00:05:15.440 --> 00:05:17.900 align:middle line:90%
encrypts through the rsa key.

00:05:17.900 --> 00:05:27.790 align:middle line:84%
So we'll run the
ssh-hostkey, passing

00:05:27.790 --> 00:05:37.060 align:middle line:84%
some arguments, script args,
of ssh hostkey equal to,

00:05:37.060 --> 00:05:38.170 align:middle line:90%
and then we'll say full.

00:05:38.170 --> 00:05:46.730 align:middle line:90%


00:05:46.730 --> 00:05:51.140 align:middle line:84%
And it gives us the
full ssh rsa hostkey.

00:05:51.140 --> 00:05:52.400 align:middle line:90%
Definitely want to save this.

00:05:52.400 --> 00:05:53.930 align:middle line:90%
That could be very useful later.

00:05:53.930 --> 00:05:58.290 align:middle line:90%


00:05:58.290 --> 00:06:01.430 align:middle line:84%
A couple more
things we can check.

00:06:01.430 --> 00:06:05.933 align:middle line:84%
Let's see if there are any
weak passwords for ssh.

00:06:05.933 --> 00:06:07.100 align:middle line:90%
We'll go back to our script.

00:06:07.100 --> 00:06:10.640 align:middle line:90%


00:06:10.640 --> 00:06:12.190 align:middle line:84%
And what we want
to check for here

00:06:12.190 --> 00:06:22.780 align:middle line:84%
is ssh-auth-methods to know what
sort of authorization methods

00:06:22.780 --> 00:06:32.440 align:middle line:84%
are being used for, in this
case, ssh.user of student.

00:06:32.440 --> 00:06:33.860 align:middle line:90%
It's always the intern.

00:06:33.860 --> 00:06:40.190 align:middle line:90%


00:06:40.190 --> 00:06:43.440 align:middle line:84%
And we see that there are
no supported authentication

00:06:43.440 --> 00:06:48.545 align:middle line:90%
methods for the user of student.

00:06:48.545 --> 00:06:51.890 align:middle line:90%


00:06:51.890 --> 00:06:52.850 align:middle line:90%
Well, that's dangerous.

00:06:52.850 --> 00:06:56.775 align:middle line:90%
Let's try it for admin.

00:06:56.775 --> 00:07:05.590 align:middle line:90%


00:07:05.590 --> 00:07:08.710 align:middle line:84%
And we see that for
the admin, there's

00:07:08.710 --> 00:07:09.910 align:middle line:90%
a public key and a password.

00:07:09.910 --> 00:07:14.810 align:middle line:90%


00:07:14.810 --> 00:07:19.820 align:middle line:84%
So we saw that student doesn't
actually have a password.

00:07:19.820 --> 00:07:33.110 align:middle line:84%
So what we could do is a ssh
student at the IP address.

00:07:33.110 --> 00:07:35.348 align:middle line:90%
And we're in.

00:07:35.348 --> 00:07:36.890 align:middle line:84%
We didn't have to
tell it a password.

00:07:36.890 --> 00:07:37.515 align:middle line:90%
We are student.

00:07:37.515 --> 00:07:50.240 align:middle line:90%


00:07:50.240 --> 00:07:51.950 align:middle line:84%
And it looks like
it's a restricted user

00:07:51.950 --> 00:07:57.530 align:middle line:90%
and doesn't have full controls.

00:07:57.530 --> 00:08:05.875 align:middle line:90%


00:08:05.875 --> 00:08:07.250 align:middle line:84%
But we can close
that connection,

00:08:07.250 --> 00:08:09.020 align:middle line:84%
and we're back on
our own machine.

00:08:09.020 --> 00:08:14.150 align:middle line:90%


00:08:14.150 --> 00:08:16.195 align:middle line:84%
But generally,
that's how SSH works.

00:08:16.195 --> 00:08:22.550 align:middle line:90%


00:08:22.550 --> 00:08:25.770 align:middle line:84%
We were able to enumerate
the SSH service,

00:08:25.770 --> 00:08:31.020 align:middle line:84%
find out that the administrator
used a password or a key.

00:08:31.020 --> 00:08:36.059 align:middle line:84%
We were able to pull
the RSA hostkey.

00:08:36.059 --> 00:08:40.590 align:middle line:84%
And we also saw that there
was an unauthenticated user

00:08:40.590 --> 00:08:41.850 align:middle line:90%
of student.

00:08:41.850 --> 00:08:47.630 align:middle line:84%
That allowed us to actually
pull a file remotely.

00:08:47.630 --> 00:08:50.380 align:middle line:90%
So that was enumeration for SSH.

00:08:50.380 --> 00:08:52.500 align:middle line:90%
We'll get a little bit deeper.

00:08:52.500 --> 00:08:53.000 align:middle line:90%