WEBVTT

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


00:00:03.936 --> 00:00:06.888 align:middle line:90%
[MUSIC PLAYING]

00:00:06.888 --> 00:00:10.350 align:middle line:90%


00:00:10.350 --> 00:00:12.030 align:middle line:90%
Banner grabbing.

00:00:12.030 --> 00:00:14.100 align:middle line:84%
Welcome to the
vulnerability scanning

00:00:14.100 --> 00:00:15.760 align:middle line:90%
section of this course.

00:00:15.760 --> 00:00:18.480 align:middle line:84%
So the first step during
the exploitation phase

00:00:18.480 --> 00:00:21.690 align:middle line:84%
of a penetration test,
will typically identify

00:00:21.690 --> 00:00:24.930 align:middle line:84%
or will involve
identifying services

00:00:24.930 --> 00:00:28.410 align:middle line:84%
that are running on the
target, as well as identifying

00:00:28.410 --> 00:00:31.990 align:middle line:84%
whether these services are
vulnerable to exploitation.

00:00:31.990 --> 00:00:35.250 align:middle line:84%
However, before we start
moving into identifying

00:00:35.250 --> 00:00:37.200 align:middle line:84%
whether these
services are indeed

00:00:37.200 --> 00:00:39.990 align:middle line:84%
vulnerable to exploitation,
the first step

00:00:39.990 --> 00:00:42.690 align:middle line:84%
will involve identifying
the service running

00:00:42.690 --> 00:00:46.560 align:middle line:84%
on a particular target, as
well as the service version.

00:00:46.560 --> 00:00:49.980 align:middle line:84%
And all of this will tie
into the process of finding

00:00:49.980 --> 00:00:52.140 align:middle line:90%
or searching for exploits.

00:00:52.140 --> 00:00:54.960 align:middle line:84%
All right, so let's get started
by getting an understanding

00:00:54.960 --> 00:00:56.910 align:middle line:90%
of what banner grabbing is.

00:00:56.910 --> 00:00:59.760 align:middle line:84%
All right, so banner grabbing
is an information gathering

00:00:59.760 --> 00:01:02.310 align:middle line:84%
technique that is used
by penetration testers

00:01:02.310 --> 00:01:05.820 align:middle line:84%
or adversaries to enumerate
information regarding

00:01:05.820 --> 00:01:08.250 align:middle line:84%
the target operating
system, as well as

00:01:08.250 --> 00:01:11.610 align:middle line:84%
these services that are
running on its open ports.

00:01:11.610 --> 00:01:14.310 align:middle line:84%
So the primary objective
of banner grabbing,

00:01:14.310 --> 00:01:17.970 align:middle line:84%
is to identify the service
running on a specific port,

00:01:17.970 --> 00:01:20.320 align:middle line:90%
as well as the service version.

00:01:20.320 --> 00:01:21.940 align:middle line:90%
So why is this important?

00:01:21.940 --> 00:01:25.740 align:middle line:84%
Well, let's say
you're essentially

00:01:25.740 --> 00:01:27.360 align:middle line:84%
assigned to perform
a penetration

00:01:27.360 --> 00:01:29.100 align:middle line:90%
test on a single system.

00:01:29.100 --> 00:01:30.090 align:middle line:90%
It could be Windows.

00:01:30.090 --> 00:01:30.930 align:middle line:90%
It could be Linux.

00:01:30.930 --> 00:01:32.470 align:middle line:90%
It really doesn't matter.

00:01:32.470 --> 00:01:33.760 align:middle line:90%
So where do you start?

00:01:33.760 --> 00:01:35.520 align:middle line:84%
Well, you start off
by performing an Nmap

00:01:35.520 --> 00:01:37.600 align:middle line:90%
scan to identify open ports.

00:01:37.600 --> 00:01:40.440 align:middle line:84%
However, your next
logical step, would

00:01:40.440 --> 00:01:42.240 align:middle line:84%
be to identify
these services that

00:01:42.240 --> 00:01:45.780 align:middle line:84%
are running on those open
ports, as well as those service

00:01:45.780 --> 00:01:46.740 align:middle line:90%
versions.

00:01:46.740 --> 00:01:48.870 align:middle line:84%
How is this
information important?

00:01:48.870 --> 00:01:50.940 align:middle line:84%
Well, the next
logical step would

00:01:50.940 --> 00:01:54.510 align:middle line:84%
be to utilize the service, as
well as the service version

00:01:54.510 --> 00:01:58.230 align:middle line:84%
information, to identify
vulnerabilities or exploits

00:01:58.230 --> 00:02:01.530 align:middle line:84%
pertinent to that specific
version of whatever service is

00:02:01.530 --> 00:02:03.900 align:middle line:90%
running on a particular port.

00:02:03.900 --> 00:02:06.480 align:middle line:84%
So banner grabbing
is fairly simple

00:02:06.480 --> 00:02:09.900 align:middle line:84%
and can be performed
through a plethora of tools

00:02:09.900 --> 00:02:11.039 align:middle line:90%
or techniques.

00:02:11.039 --> 00:02:14.460 align:middle line:84%
An example of this would be
to perform service version

00:02:14.460 --> 00:02:16.590 align:middle line:84%
detection or to
perform banner grabbing

00:02:16.590 --> 00:02:20.130 align:middle line:84%
with Nmap through the use of
the service version detection

00:02:20.130 --> 00:02:22.740 align:middle line:84%
scan, which you should
be familiar with by now.

00:02:22.740 --> 00:02:24.930 align:middle line:84%
You can also connect
to the open port

00:02:24.930 --> 00:02:28.590 align:middle line:84%
on the target using Netcat, and
that is the de facto technique

00:02:28.590 --> 00:02:30.630 align:middle line:84%
that is utilized by
penetration testers,

00:02:30.630 --> 00:02:32.940 align:middle line:84%
as it is the most
accurate, and you'll

00:02:32.940 --> 00:02:34.690 align:middle line:90%
see why in a few seconds.

00:02:34.690 --> 00:02:37.020 align:middle line:84%
And you also have the
ability to authenticate

00:02:37.020 --> 00:02:40.230 align:middle line:84%
with the service, that is
if the service supports

00:02:40.230 --> 00:02:41.490 align:middle line:90%
authentication.

00:02:41.490 --> 00:02:45.270 align:middle line:84%
For example, you can perform
banner grabbing on SSH

00:02:45.270 --> 00:02:48.810 align:middle line:84%
by simply trying to
authenticate with the SSH server

00:02:48.810 --> 00:02:51.210 align:middle line:84%
with the SSH client,
and that, of course,

00:02:51.210 --> 00:02:53.580 align:middle line:84%
works for any
protocol or service

00:02:53.580 --> 00:02:55.020 align:middle line:90%
that supports authentication.

00:02:55.020 --> 00:02:58.592 align:middle line:84%
That could be SSH, FTP,
Telnet, et cetera, et cetera.

00:02:58.592 --> 00:03:00.300 align:middle line:84%
So we're going to be
taking a look at how

00:03:00.300 --> 00:03:03.000 align:middle line:84%
to do all of this within
the practical demonstration

00:03:03.000 --> 00:03:04.620 align:middle line:90%
of this video.

00:03:04.620 --> 00:03:07.712 align:middle line:84%
This particular video has
a lab environment set up.

00:03:07.712 --> 00:03:09.420 align:middle line:84%
So all you need to do
is just fire it up,

00:03:09.420 --> 00:03:12.060 align:middle line:84%
and you'll be able to follow
along with the techniques

00:03:12.060 --> 00:03:14.348 align:middle line:84%
that I'll highlight
in a few seconds.

00:03:14.348 --> 00:03:16.140 align:middle line:84%
So I'm going to fire
up my lab environment,

00:03:16.140 --> 00:03:19.490 align:middle line:84%
and I'll see you within
the lab environment.

00:03:19.490 --> 00:03:22.470 align:middle line:84%
All right, so I'm back
within the lab environment.

00:03:22.470 --> 00:03:25.730 align:middle line:84%
And the first step, will involve
identifying the target IP

00:03:25.730 --> 00:03:29.300 align:middle line:84%
address that we are going to be
performing banner grabbing on.

00:03:29.300 --> 00:03:32.660 align:middle line:84%
So in order to obtain the
target IP address, just type

00:03:32.660 --> 00:03:35.990 align:middle line:84%
in ifconfig and take a look
at the interface ethernet 1.

00:03:35.990 --> 00:03:38.250 align:middle line:84%
So this is going to
be your IP address.

00:03:38.250 --> 00:03:41.490 align:middle line:84%
Now, in your case, the subnet
is going to be different.

00:03:41.490 --> 00:03:43.340 align:middle line:84%
However, the target
IP address will

00:03:43.340 --> 00:03:46.820 align:middle line:84%
be on the next IP
within the subnet range.

00:03:46.820 --> 00:03:49.730 align:middle line:84%
So for example, if
the attacker's IP

00:03:49.730 --> 00:03:53.420 align:middle line:84%
is on the second IP address,
the target IP address

00:03:53.420 --> 00:03:55.410 align:middle line:84%
is going to be on
the third IP address.

00:03:55.410 --> 00:03:57.680 align:middle line:84%
So irregardless of
what the subnet is,

00:03:57.680 --> 00:04:01.490 align:middle line:84%
just copy this value here
and change the 2 to a 3,

00:04:01.490 --> 00:04:03.710 align:middle line:90%
and that's the target IP.

00:04:03.710 --> 00:04:06.470 align:middle line:84%
So now that we've identified
the target IP address,

00:04:06.470 --> 00:04:10.520 align:middle line:84%
we can move on to the next step,
which essentially, involves

00:04:10.520 --> 00:04:11.720 align:middle line:90%
performing banner grabbing.

00:04:11.720 --> 00:04:15.110 align:middle line:84%
So the first tool we'll be
taking a look at, is Nmap.

00:04:15.110 --> 00:04:17.930 align:middle line:84%
Now, you should be fairly
comfortable with using Nmap,

00:04:17.930 --> 00:04:19.820 align:middle line:84%
and, again, I'm just
going to go through this

00:04:19.820 --> 00:04:21.829 align:middle line:84%
and show you a few
of the techniques

00:04:21.829 --> 00:04:24.710 align:middle line:84%
that you might not have been
aware of when it comes down

00:04:24.710 --> 00:04:25.550 align:middle line:90%
to using Nmap.

00:04:25.550 --> 00:04:29.540 align:middle line:84%
So in order to identify
the services that

00:04:29.540 --> 00:04:32.480 align:middle line:84%
are running on a target
system or on the open ports

00:04:32.480 --> 00:04:35.660 align:middle line:84%
on a target system, as well
as the target operating

00:04:35.660 --> 00:04:38.690 align:middle line:84%
system itself and the
version of operating system

00:04:38.690 --> 00:04:40.400 align:middle line:90%
that is running on the target.

00:04:40.400 --> 00:04:43.130 align:middle line:84%
We can, essentially,
launch an Nmap scan

00:04:43.130 --> 00:04:44.730 align:middle line:90%
with the following arguments.

00:04:44.730 --> 00:04:47.540 align:middle line:84%
So we will perform the standard
service-version detection

00:04:47.540 --> 00:04:50.330 align:middle line:84%
scan, which will not only tell
us what services are running

00:04:50.330 --> 00:04:53.180 align:middle line:84%
on the open ports on
the target, it'll also

00:04:53.180 --> 00:04:55.280 align:middle line:90%
tell us the service versions.

00:04:55.280 --> 00:04:58.460 align:middle line:84%
We can then perform operating
system scan, and operating

00:04:58.460 --> 00:05:00.320 align:middle line:84%
system scan, that will,
essentially, give us

00:05:00.320 --> 00:05:03.780 align:middle line:84%
a rough estimate as to what
is running on the target,

00:05:03.780 --> 00:05:06.290 align:middle line:84%
whether it's running Windows,
whether it's running Linux,

00:05:06.290 --> 00:05:08.600 align:middle line:84%
and in the case of
Linux, it could give us

00:05:08.600 --> 00:05:12.040 align:middle line:84%
the actual distribution
release name.

00:05:12.040 --> 00:05:13.940 align:middle line:84%
We can then paste
in the target IP.

00:05:13.940 --> 00:05:17.558 align:middle line:84%
Remember to change the 2 to
a 3, and we can hit Enter.

00:05:17.558 --> 00:05:19.975 align:middle line:84%
So I'm going to give this a
couple of seconds to complete.

00:05:19.975 --> 00:05:22.930 align:middle line:90%


00:05:22.930 --> 00:05:24.550 align:middle line:84%
All right, the
Nmap scan is done.

00:05:24.550 --> 00:05:27.780 align:middle line:84%
And as you can see, we only have
one port open on the target.

00:05:27.780 --> 00:05:29.860 align:middle line:84%
That is port 22,
which of course,

00:05:29.860 --> 00:05:33.210 align:middle line:90%
is SSH and that is a TCP port.

00:05:33.210 --> 00:05:35.430 align:middle line:84%
And you can see under
the version column

00:05:35.430 --> 00:05:37.050 align:middle line:84%
here, that it
actually enumerates

00:05:37.050 --> 00:05:38.710 align:middle line:90%
the actual service itself.

00:05:38.710 --> 00:05:40.710 align:middle line:84%
So it tells us that
it is indeed running.

00:05:40.710 --> 00:05:41.860 align:middle line:90%
SSH.

00:05:41.860 --> 00:05:43.780 align:middle line:84%
However, it tells us
the service version.

00:05:43.780 --> 00:05:50.340 align:middle line:84%
So it is running OpenSSH 7.2p2
OpenSSH is a very popular open

00:05:50.340 --> 00:05:55.650 align:middle line:84%
source SSH server that is
typically installed on Linux,

00:05:55.650 --> 00:06:00.790 align:middle line:84%
as well as Windows, so it gives
us the exact service name,

00:06:00.790 --> 00:06:04.710 align:middle line:84%
which is OpenSSH and the
service version, which is 7.2p2.

00:06:04.710 --> 00:06:06.690 align:middle line:84%
And it also, in
this case, gives us

00:06:06.690 --> 00:06:09.270 align:middle line:84%
a rough idea as to what
operating system is

00:06:09.270 --> 00:06:10.380 align:middle line:90%
running on the target.

00:06:10.380 --> 00:06:13.920 align:middle line:84%
In this case, you can see,
the target is running Ubuntu.

00:06:13.920 --> 00:06:16.260 align:middle line:84%
And that is very, very
important information.

00:06:16.260 --> 00:06:18.900 align:middle line:84%
And I'll get to why that is
important, in a few seconds,

00:06:18.900 --> 00:06:22.060 align:middle line:84%
from the perspective of
a penetration tester.

00:06:22.060 --> 00:06:24.833 align:middle line:84%
Now, one really cool thing
that you can do with Nmap,

00:06:24.833 --> 00:06:26.250 align:middle line:84%
and, of course,
we'll be exploring

00:06:26.250 --> 00:06:29.190 align:middle line:84%
this in the next video,
is the utilization

00:06:29.190 --> 00:06:32.100 align:middle line:84%
of Nmap scripts or the
Nmap scripting engine.

00:06:32.100 --> 00:06:33.990 align:middle line:84%
Now, in terms of
banner grabbing,

00:06:33.990 --> 00:06:36.330 align:middle line:84%
there exists a very
cool script that

00:06:36.330 --> 00:06:38.310 align:middle line:84%
can be found under
the default storage

00:06:38.310 --> 00:06:40.750 align:middle line:90%
directory for Nmap scripts.

00:06:40.750 --> 00:06:45.360 align:middle line:84%
So if we list out the contents
of usr/share/nmap/scripts,

00:06:45.360 --> 00:06:47.800 align:middle line:84%
and we can then
pipe out the output.

00:06:47.800 --> 00:06:50.430 align:middle line:84%
And we can then grep
for a specific script

00:06:50.430 --> 00:06:51.600 align:middle line:90%
that we're looking for.

00:06:51.600 --> 00:06:54.840 align:middle line:84%
In this case, the name
of the script is banner.

00:06:54.840 --> 00:06:58.530 align:middle line:84%
So the banner.nsc or
the banner Nmap script

00:06:58.530 --> 00:07:01.830 align:middle line:84%
can be used to identify
the actual service banner.

00:07:01.830 --> 00:07:04.560 align:middle line:84%
So again, a banner
is essentially

00:07:04.560 --> 00:07:07.920 align:middle line:84%
used for logistical
purposes in that it

00:07:07.920 --> 00:07:10.620 align:middle line:84%
tells a user or
anyone who is trying

00:07:10.620 --> 00:07:13.680 align:middle line:84%
to access that
particular service, what

00:07:13.680 --> 00:07:15.330 align:middle line:84%
is running on that
particular port,

00:07:15.330 --> 00:07:17.100 align:middle line:90%
as well as the service version.

00:07:17.100 --> 00:07:20.910 align:middle line:84%
Now, banners can be changed,
but by default, that information

00:07:20.910 --> 00:07:22.720 align:middle line:90%
should be obtainable.

00:07:22.720 --> 00:07:25.860 align:middle line:84%
So if we wanted to use this
particular Nmap script,

00:07:25.860 --> 00:07:27.900 align:middle line:90%
we could say, for example, Nmap.

00:07:27.900 --> 00:07:30.870 align:middle line:84%
And then we can perform a
service-version detection scan

00:07:30.870 --> 00:07:32.370 align:middle line:90%
and then use the script.

00:07:32.370 --> 00:07:35.020 align:middle line:84%
Although, this will be
redundant, and you'll see why.

00:07:35.020 --> 00:07:37.440 align:middle line:84%
And we can say we want
to use the banner script.

00:07:37.440 --> 00:07:41.040 align:middle line:84%
We don't need to provide the
extension, which is the .nsc.

00:07:41.040 --> 00:07:43.170 align:middle line:84%
And then we can paste
in the target IP,

00:07:43.170 --> 00:07:45.360 align:middle line:90%
and I'll change the 2 to 3 here.

00:07:45.360 --> 00:07:48.090 align:middle line:84%
And lets hit Enter, and
let's see what output we get.

00:07:48.090 --> 00:07:50.040 align:middle line:84%
So you can see that
Nmap will perform

00:07:50.040 --> 00:07:52.330 align:middle line:84%
its typical service-version
detection scan.

00:07:52.330 --> 00:07:55.710 align:middle line:84%
So it tells us it's
running OpenSSH 7.2p2.

00:07:55.710 --> 00:07:58.027 align:middle line:84%
And for the actual
script results,

00:07:58.027 --> 00:07:59.610 align:middle line:84%
you can see this is
the banner script.

00:07:59.610 --> 00:08:01.560 align:middle line:84%
It gives us, pretty much,
the same information

00:08:01.560 --> 00:08:04.060 align:middle line:84%
that we would have gotten
if we had performed

00:08:04.060 --> 00:08:06.900 align:middle line:84%
the scan with a typical
service-version detection

00:08:06.900 --> 00:08:08.760 align:middle line:90%
parameters specified.

00:08:08.760 --> 00:08:12.870 align:middle line:84%
Again, this is just a really
quick and cool Nmap script

00:08:12.870 --> 00:08:15.270 align:middle line:84%
that can be used to
perform banner grabbing

00:08:15.270 --> 00:08:19.020 align:middle line:84%
on particular services
that might not necessarily

00:08:19.020 --> 00:08:21.450 align:middle line:84%
reveal what service
version is running

00:08:21.450 --> 00:08:24.930 align:middle line:84%
when you perform a standard
service-version detection scan.

00:08:24.930 --> 00:08:28.470 align:middle line:84%
And you'll actually come
across quite a few services

00:08:28.470 --> 00:08:31.851 align:middle line:84%
that you're not be able to
identify what is running,

00:08:31.851 --> 00:08:33.809 align:middle line:84%
as well as the service
version, and this script

00:08:33.809 --> 00:08:36.159 align:middle line:90%
can be quite helpful.

00:08:36.159 --> 00:08:39.580 align:middle line:84%
So that is how to perform
banner grabbing with Nmap.

00:08:39.580 --> 00:08:41.950 align:middle line:84%
The next tool, of
course, is Netcat.

00:08:41.950 --> 00:08:44.975 align:middle line:84%
Now, again, I will be covering
Netcat in its own section

00:08:44.975 --> 00:08:46.600 align:middle line:84%
within this course,
but for now, if you

00:08:46.600 --> 00:08:48.670 align:middle line:84%
want to learn more
about what Netcat is,

00:08:48.670 --> 00:08:54.620 align:middle line:84%
I can say what is, for example,
what is Netcat, and that is nc.

00:08:54.620 --> 00:08:58.230 align:middle line:84%
Hit Enter and you can see this
is the TCP/IP Swiss army knife.

00:08:58.230 --> 00:08:58.880 align:middle line:90%
It really is.

00:08:58.880 --> 00:09:00.750 align:middle line:90%
It's an extremely powerful tool.

00:09:00.750 --> 00:09:04.580 align:middle line:84%
So I can also open up the man
pages for the Netcat utility,

00:09:04.580 --> 00:09:06.655 align:middle line:84%
and you can learn
more about it here.

00:09:06.655 --> 00:09:08.030 align:middle line:84%
However, in this
case, we're just

00:09:08.030 --> 00:09:10.020 align:middle line:84%
going to be going through
a simple scenario.

00:09:10.020 --> 00:09:12.140 align:middle line:84%
So for example, we
know that the target

00:09:12.140 --> 00:09:14.570 align:middle line:90%
is running SSH on port 22.

00:09:14.570 --> 00:09:17.540 align:middle line:84%
We can perform banner grabbing
with Netcat by simply saying

00:09:17.540 --> 00:09:21.950 align:middle line:84%
nc, pasting in the target IP,
and then the port that we would

00:09:21.950 --> 00:09:25.400 align:middle line:84%
like to perform banner grabbing
on, in this case, it's port 22.

00:09:25.400 --> 00:09:28.550 align:middle line:84%
We hit Enter, and you can
see it tells us or gives us

00:09:28.550 --> 00:09:31.040 align:middle line:84%
the exact banner that we would
have gotten if we would have

00:09:31.040 --> 00:09:32.660 align:middle line:90%
performed the scan with Nmap.

00:09:32.660 --> 00:09:35.540 align:middle line:84%
However, as I said, many
penetration testers still

00:09:35.540 --> 00:09:39.350 align:middle line:84%
rely on Netcat, as
in certain scenarios,

00:09:39.350 --> 00:09:41.060 align:middle line:84%
Nmap might not be
able to give you

00:09:41.060 --> 00:09:44.130 align:middle line:84%
an accurate idea of
what service is running,

00:09:44.130 --> 00:09:45.810 align:middle line:90%
as well as the service version.

00:09:45.810 --> 00:09:48.020 align:middle line:84%
So you can always
rely on Netcat.

00:09:48.020 --> 00:09:50.285 align:middle line:84%
Netcat has always got
your back on this.

00:09:50.285 --> 00:09:52.160 align:middle line:84%
So you can see it gives
us the actual banner.

00:09:52.160 --> 00:09:54.420 align:middle line:84%
Now, you might be
asking yourself, well,

00:09:54.420 --> 00:09:56.340 align:middle line:84%
why is this
information important?

00:09:56.340 --> 00:09:59.990 align:middle line:84%
Well, a penetration tester will
typically take this information

00:09:59.990 --> 00:10:02.600 align:middle line:84%
and utilize a tool
like searchsploit,

00:10:02.600 --> 00:10:04.340 align:middle line:90%
which I will cover later on.

00:10:04.340 --> 00:10:07.280 align:middle line:84%
They could say, searchsploit
and then they could essentially

00:10:07.280 --> 00:10:10.400 align:middle line:84%
search for exploits pertinent
to this specific version

00:10:10.400 --> 00:10:11.330 align:middle line:90%
of OpenSSH.

00:10:11.330 --> 00:10:16.370 align:middle line:84%
So I can say, searchsploit
open SSH 7.2, hit Enter.

00:10:16.370 --> 00:10:20.720 align:middle line:84%
And you can see
that OpenSSH 7.2 is

00:10:20.720 --> 00:10:23.670 align:middle line:84%
vulnerable to the following
exploits or vulnerability.

00:10:23.670 --> 00:10:26.600 align:middle line:84%
So it's vulnerable
to denial of service.

00:10:26.600 --> 00:10:30.890 align:middle line:84%
7.2p1, now remember, we're
looking for p2 vulnerabilities,

00:10:30.890 --> 00:10:36.800 align:middle line:84%
is vulnerable to authenticated
XOF command injection and 7.2p2

00:10:36.800 --> 00:10:39.180 align:middle line:84%
is vulnerable to
username enumeration.

00:10:39.180 --> 00:10:41.930 align:middle line:84%
So immediately, an attacker
is able to identify

00:10:41.930 --> 00:10:44.720 align:middle line:84%
what they can do in
terms of exploitation

00:10:44.720 --> 00:10:47.580 align:middle line:90%
to this particular service.

00:10:47.580 --> 00:10:50.940 align:middle line:84%
So that is how to perform
banner grabbing with Netcat.

00:10:50.940 --> 00:10:53.610 align:middle line:84%
Now, as I said, in
certain scenarios,

00:10:53.610 --> 00:10:56.640 align:middle line:84%
a particular service may
support authentication.

00:10:56.640 --> 00:10:59.620 align:middle line:84%
And in this case, SSH does
support authentication.

00:10:59.620 --> 00:11:01.680 align:middle line:84%
So you can also
retrieve the banner

00:11:01.680 --> 00:11:05.010 align:middle line:84%
by authenticating with
the target system via SSH,

00:11:05.010 --> 00:11:07.260 align:middle line:84%
and, of course, you don't
need legitimate credentials.

00:11:07.260 --> 00:11:11.830 align:middle line:84%
I could say, ssh root there
type in the target IP.

00:11:11.830 --> 00:11:15.590 align:middle line:84%
In this case, I'll just change
the 2 to 3 and hit Enter.

00:11:15.590 --> 00:11:17.610 align:middle line:84%
And we'll give this
a couple of seconds.

00:11:17.610 --> 00:11:20.540 align:middle line:84%
And you can see that instead of
printing the service version,

00:11:20.540 --> 00:11:23.217 align:middle line:84%
it prints out the
SSH welcome banner.

00:11:23.217 --> 00:11:25.550 align:middle line:84%
Now as I said, this is something
that's not very common,

00:11:25.550 --> 00:11:29.120 align:middle line:84%
but in some cases, this
particular technique

00:11:29.120 --> 00:11:31.250 align:middle line:84%
might not reveal
anything of importance

00:11:31.250 --> 00:11:34.970 align:middle line:84%
to you from the perspective
of a penetration tester.

00:11:34.970 --> 00:11:36.770 align:middle line:84%
So you can see in
this case, it's just

00:11:36.770 --> 00:11:38.670 align:middle line:90%
printing out a welcome message.

00:11:38.670 --> 00:11:40.290 align:middle line:90%
So that's really not helpful.

00:11:40.290 --> 00:11:43.220 align:middle line:84%
However, for other services
that support authentication,

00:11:43.220 --> 00:11:46.940 align:middle line:84%
like FTP or Telnet, you
can also try and utilize

00:11:46.940 --> 00:11:48.980 align:middle line:84%
the standard
authentication client

00:11:48.980 --> 00:11:53.450 align:middle line:84%
to identify a banner or
information that can be useful

00:11:53.450 --> 00:11:55.970 align:middle line:90%
later on during exploitation.

00:11:55.970 --> 00:11:57.660 align:middle line:84%
Because I don't have
the credentials,

00:11:57.660 --> 00:12:00.110 align:middle line:84%
I'll just terminate that
particular authentication

00:12:00.110 --> 00:12:01.220 align:middle line:90%
attempt.

00:12:01.220 --> 00:12:04.790 align:middle line:84%
So that is how to perform banner
grabbing with Nmap, Netcat,

00:12:04.790 --> 00:12:08.120 align:middle line:84%
as well as the
relevant authentication

00:12:08.120 --> 00:12:10.100 align:middle line:84%
clients pertinent to
the service that's

00:12:10.100 --> 00:12:11.990 align:middle line:90%
running on a target system.

00:12:11.990 --> 00:12:15.050 align:middle line:84%
And this is going to conclude
the practical demonstration

00:12:15.050 --> 00:12:17.850 align:middle line:90%
side of this video.

00:12:17.850 --> 00:12:19.850 align:middle line:84%
All right, so in the
next video, we're

00:12:19.850 --> 00:12:23.420 align:middle line:84%
going to be taking a deeper look
at the Nmap scripting engine,

00:12:23.420 --> 00:12:26.390 align:middle line:84%
in context or in the
context of exploitation

00:12:26.390 --> 00:12:29.462 align:middle line:84%
and identifying and
testing vulnerabilities.

00:12:29.462 --> 00:12:30.920 align:middle line:84%
And again, we'll
take a look at how

00:12:30.920 --> 00:12:34.730 align:middle line:84%
to utilize Nmap scripts
to identify or to check

00:12:34.730 --> 00:12:38.360 align:middle line:84%
whether a particular service
or whether a particular target

00:12:38.360 --> 00:12:40.680 align:middle line:84%
is vulnerable to a
particular exploit.

00:12:40.680 --> 00:12:43.500 align:middle line:84%
So I'll see you
in the next video.

00:12:43.500 --> 00:12:44.000 align:middle line:90%