WEBVTT

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


00:00:10.050 --> 00:00:15.060 align:middle line:84%
Exploiting the Bash
Vulnerability CVE-2014-6271,

00:00:15.060 --> 00:00:17.110 align:middle line:90%
also known as Shellshock.

00:00:17.110 --> 00:00:17.610 align:middle line:90%
All right.

00:00:17.610 --> 00:00:20.760 align:middle line:84%
So we're now getting started
with the Linux exploitation

00:00:20.760 --> 00:00:22.110 align:middle line:90%
section of this course.

00:00:22.110 --> 00:00:25.080 align:middle line:84%
And the first vulnerability
that we're going to be exploring

00:00:25.080 --> 00:00:27.030 align:middle line:90%
is the Shellshock vulnerability.

00:00:27.030 --> 00:00:29.550 align:middle line:84%
Now, the interesting thing
about this vulnerability

00:00:29.550 --> 00:00:32.970 align:middle line:84%
is it was probably one of the
biggest vulnerabilities that

00:00:32.970 --> 00:00:35.700 align:middle line:84%
affected Linux over
the last, I would say,

00:00:35.700 --> 00:00:39.660 align:middle line:84%
over the last 15 to 20
years, and for a good reason.

00:00:39.660 --> 00:00:43.900 align:middle line:84%
And again, the reason that
makes this vulnerability

00:00:43.900 --> 00:00:47.820 align:middle line:84%
so dangerous or critical in
regards to a Linux system

00:00:47.820 --> 00:00:50.460 align:middle line:84%
is the fact that it
essentially allows an attacker

00:00:50.460 --> 00:00:54.450 align:middle line:84%
to remotely execute arbitrary
commands on the Linux target.

00:00:54.450 --> 00:00:58.350 align:middle line:84%
And the exploitation
of this vulnerability

00:00:58.350 --> 00:01:01.590 align:middle line:84%
really involves two services--
one of them is Apache,

00:01:01.590 --> 00:01:03.879 align:middle line:84%
and the second one,
of course, is Bash.

00:01:03.879 --> 00:01:04.379 align:middle line:90%
All right.

00:01:04.379 --> 00:01:06.420 align:middle line:84%
So let's learn more
about this vulnerability.

00:01:06.420 --> 00:01:11.010 align:middle line:84%
Shellshock is the name given
to a family of vulnerabilities

00:01:11.010 --> 00:01:15.270 align:middle line:84%
in the Bash shell since version
1.3, which was released,

00:01:15.270 --> 00:01:17.580 align:middle line:90%
I think, somewhere in the '90s.

00:01:17.580 --> 00:01:23.160 align:middle line:84%
So again, it really affected
a huge number of Bash versions

00:01:23.160 --> 00:01:25.800 align:middle line:90%
after version 1.3.

00:01:25.800 --> 00:01:27.240 align:middle line:84%
So this vulnerability
essentially

00:01:27.240 --> 00:01:30.510 align:middle line:84%
allows an attacker to execute
remote arbitrary commands

00:01:30.510 --> 00:01:33.510 align:middle line:84%
via Bash, consequently
allowing the attacker

00:01:33.510 --> 00:01:36.900 align:middle line:84%
to obtain remote access to the
target via a reverse shell.

00:01:36.900 --> 00:01:39.400 align:middle line:84%
And that's where it
primarily gets its name from,

00:01:39.400 --> 00:01:40.980 align:middle line:90%
so Shellshock.

00:01:40.980 --> 00:01:43.440 align:middle line:84%
That tells you that
in there somewhere,

00:01:43.440 --> 00:01:45.570 align:middle line:84%
or rather, this vulnerability
allows an attacker

00:01:45.570 --> 00:01:49.260 align:middle line:84%
to get a shell on
the target system.

00:01:49.260 --> 00:01:52.890 align:middle line:84%
The Shellshock vulnerability
was discovered by Stéphane

00:01:52.890 --> 00:01:53.970 align:middle line:90%
Chazelas--

00:01:53.970 --> 00:01:55.620 align:middle line:84%
I hope I'm not
mispronouncing that--

00:01:55.620 --> 00:01:59.760 align:middle line:84%
on the 12th of September
2014 and was made public

00:01:59.760 --> 00:02:02.310 align:middle line:90%
on the 24th of September 2014.

00:02:02.310 --> 00:02:06.270 align:middle line:84%
So again, given the
actual critical nature

00:02:06.270 --> 00:02:09.030 align:middle line:84%
of this vulnerability, patches
were released soon after.

00:02:09.030 --> 00:02:12.390 align:middle line:84%
And of course, companies
and organizations as well as

00:02:12.390 --> 00:02:14.730 align:middle line:84%
individuals were
actually informed

00:02:14.730 --> 00:02:18.640 align:middle line:84%
to update their versions of
Bash as soon as possible.

00:02:18.640 --> 00:02:23.700 align:middle line:84%
However, given the current
fragmented nature of the Linux

00:02:23.700 --> 00:02:26.160 align:middle line:84%
world and the
various distributions

00:02:26.160 --> 00:02:29.160 align:middle line:84%
available out there, the
patching or the updated

00:02:29.160 --> 00:02:32.160 align:middle line:84%
packages were added
to repositories

00:02:32.160 --> 00:02:35.850 align:middle line:84%
based on the actual
distributions release--

00:02:35.850 --> 00:02:37.440 align:middle line:90%
the actual release cycle.

00:02:37.440 --> 00:02:40.980 align:middle line:84%
So if a distribution had
a slower release cycle,

00:02:40.980 --> 00:02:45.032 align:middle line:84%
maybe after every six
months, then packages could--

00:02:45.032 --> 00:02:46.740 align:middle line:84%
rather those distributions
could actually

00:02:46.740 --> 00:02:51.720 align:middle line:84%
be releasing the updated patches
for Bash very, very late.

00:02:51.720 --> 00:02:54.390 align:middle line:84%
However, you had the ability
to update it manually.

00:02:54.390 --> 00:02:57.720 align:middle line:84%
And that's one of the
great things about Linux.

00:02:57.720 --> 00:03:00.870 align:middle line:84%
This vulnerability really
isn't very common anymore.

00:03:00.870 --> 00:03:03.900 align:middle line:84%
But it's very important that
you actually learn about it

00:03:03.900 --> 00:03:06.930 align:middle line:84%
and get an idea as
to how to exploit it.

00:03:06.930 --> 00:03:10.680 align:middle line:84%
And this will really tie into
the web application penetration

00:03:10.680 --> 00:03:15.150 align:middle line:84%
testing course on INE as well
as the eWPT certification.

00:03:15.150 --> 00:03:17.370 align:middle line:84%
So learning about command
injection, in this case,

00:03:17.370 --> 00:03:19.000 align:middle line:90%
is very, very important.

00:03:19.000 --> 00:03:20.220 align:middle line:90%
Now, what is Bash?

00:03:20.220 --> 00:03:21.900 align:middle line:84%
If you've never
used Linux before,

00:03:21.900 --> 00:03:23.850 align:middle line:84%
Bash is essentially
a *Nix shell.

00:03:23.850 --> 00:03:27.930 align:middle line:84%
*Nix is essentially an
abbreviation for Unix-based

00:03:27.930 --> 00:03:31.780 align:middle line:84%
operating systems, and Linux is
a Unix-based operating system.

00:03:31.780 --> 00:03:35.850 align:middle line:84%
So Bash is a *Nix shell that is
part of the GNU project and is

00:03:35.850 --> 00:03:38.260 align:middle line:84%
the default shell for
most Linux distributions.

00:03:38.260 --> 00:03:41.170 align:middle line:84%
So whenever you install,
really, any distribution--

00:03:41.170 --> 00:03:45.750 align:middle line:84%
Ubuntu, Debian,
Arch, Linux, Fedora--

00:03:45.750 --> 00:03:49.320 align:middle line:84%
by default, the default
shell is going to be Bash.

00:03:49.320 --> 00:03:51.000 align:middle line:90%
Now, what is a shell?

00:03:51.000 --> 00:03:53.830 align:middle line:84%
Well, a shell is essentially
a command line interface.

00:03:53.830 --> 00:03:56.310 align:middle line:84%
So on Windows, you have
your command prompt,

00:03:56.310 --> 00:03:59.520 align:middle line:84%
and on Linux, you have
your various shells,

00:03:59.520 --> 00:04:03.680 align:middle line:84%
and Bash is the de facto
standard for most distribution.

00:04:03.680 --> 00:04:06.120 align:middle line:84%
So again, this
vulnerability really

00:04:06.120 --> 00:04:11.340 align:middle line:84%
did shake up the whole
Linux industry in regards

00:04:11.340 --> 00:04:13.470 align:middle line:90%
to vulnerabilities.

00:04:13.470 --> 00:04:15.420 align:middle line:84%
Now, the Shellshock
vulnerability

00:04:15.420 --> 00:04:17.579 align:middle line:84%
is caused by a
vulnerability in Bash,

00:04:17.579 --> 00:04:20.490 align:middle line:84%
whereby Bash mistakenly
executes trailing commands

00:04:20.490 --> 00:04:22.500 align:middle line:90%
after a series of characters.

00:04:22.500 --> 00:04:27.180 align:middle line:84%
And these characters are
really down to the fact

00:04:27.180 --> 00:04:29.820 align:middle line:84%
that there is a
vulnerability within Bash

00:04:29.820 --> 00:04:33.390 align:middle line:84%
in regards to the environment
variable function declaration.

00:04:33.390 --> 00:04:36.120 align:middle line:84%
Now, I won't get into
the actual nitty-gritty

00:04:36.120 --> 00:04:38.460 align:middle line:84%
of this vulnerability
and how it works.

00:04:38.460 --> 00:04:42.270 align:middle line:84%
All that you need to know is
that if these characters are

00:04:42.270 --> 00:04:45.870 align:middle line:84%
input into Bash, really,
any other commands

00:04:45.870 --> 00:04:48.930 align:middle line:84%
executed after these
special characters will

00:04:48.930 --> 00:04:50.550 align:middle line:90%
be executed by Bash.

00:04:50.550 --> 00:04:53.940 align:middle line:84%
Now, again, given the fact that
this vulnerability primarily

00:04:53.940 --> 00:04:56.535 align:middle line:84%
or really exclusively
affects Bash,

00:04:56.535 --> 00:04:59.910 align:middle line:84%
the vulnerability really only
affects Linux as Windows does

00:04:59.910 --> 00:05:03.820 align:middle line:84%
not utilize Bash as it is not
a *Nix-based operating system.

00:05:03.820 --> 00:05:07.820 align:middle line:84%
So this vulnerability really
was pertinent only to the Linux

00:05:07.820 --> 00:05:09.320 align:middle line:90%
operating system.

00:05:09.320 --> 00:05:12.380 align:middle line:84%
Now, in the context of
remote exploitation,

00:05:12.380 --> 00:05:15.830 align:middle line:84%
Apache web servers can be
configured to run CGI scripts

00:05:15.830 --> 00:05:20.060 align:middle line:84%
or shell scripts that are
vulnerable to this attack.

00:05:20.060 --> 00:05:22.100 align:middle line:84%
And you might be asking
yourself, well, I'm

00:05:22.100 --> 00:05:24.200 align:middle line:84%
not really understanding
what's going on here.

00:05:24.200 --> 00:05:27.140 align:middle line:84%
You're saying the vulnerability
is related to Bash,

00:05:27.140 --> 00:05:29.000 align:middle line:84%
or it's a vulnerability
within Bash,

00:05:29.000 --> 00:05:31.340 align:middle line:84%
but how does that
tie into CGI scripts?

00:05:31.340 --> 00:05:34.700 align:middle line:84%
Well, CGI, which stands for
Common Gateway Interface,

00:05:34.700 --> 00:05:38.240 align:middle line:84%
CGI scripts are used by Apache
to execute arbitrary commands

00:05:38.240 --> 00:05:41.240 align:middle line:84%
on the Linux system, after
which the output is displayed

00:05:41.240 --> 00:05:41.940 align:middle line:90%
to the client.

00:05:41.940 --> 00:05:44.043 align:middle line:84%
So if you're running
a web server,

00:05:44.043 --> 00:05:45.710 align:middle line:84%
an Apache web server,
and you're hosting

00:05:45.710 --> 00:05:47.840 align:middle line:84%
a web application
irregardless of whether it's

00:05:47.840 --> 00:05:52.400 align:middle line:84%
a PHP or HTML or anything like
that, you can create or develop

00:05:52.400 --> 00:05:55.670 align:middle line:84%
CGI scripts to essentially
obtain information

00:05:55.670 --> 00:05:56.460 align:middle line:90%
from the system.

00:05:56.460 --> 00:05:59.930 align:middle line:84%
So, for example, if I wanted
to get the current time

00:05:59.930 --> 00:06:02.960 align:middle line:84%
on the Linux server, I
could use the CGI script

00:06:02.960 --> 00:06:05.210 align:middle line:84%
to essentially execute
the time command

00:06:05.210 --> 00:06:09.320 align:middle line:84%
and then redirect or display
the output on the actual website

00:06:09.320 --> 00:06:10.200 align:middle line:90%
or the web page.

00:06:10.200 --> 00:06:13.220 align:middle line:84%
So again, many web
servers or many websites

00:06:13.220 --> 00:06:16.715 align:middle line:84%
actually utilize this
functionality to limiting--

00:06:16.715 --> 00:06:18.120 align:middle line:90%
to varying degrees.

00:06:18.120 --> 00:06:20.630 align:middle line:84%
And again, you don't
see it anymore now

00:06:20.630 --> 00:06:24.440 align:middle line:84%
for obvious reasons, primarily
because if the attacker is

00:06:24.440 --> 00:06:27.770 align:middle line:84%
able to execute the CGI
script and in the case

00:06:27.770 --> 00:06:31.610 align:middle line:84%
of this vulnerability, pass in
this special set of characters

00:06:31.610 --> 00:06:34.490 align:middle line:84%
as well as additional commands
that you would like to execute,

00:06:34.490 --> 00:06:36.620 align:middle line:84%
he could potentially
use this vulnerability

00:06:36.620 --> 00:06:40.250 align:middle line:84%
to execute arbitrary commands
that could be malicious.

00:06:40.250 --> 00:06:45.500 align:middle line:84%
So CGI scripts are used
quite a bit on Apache,

00:06:45.500 --> 00:06:47.120 align:middle line:90%
and they're very, very useful.

00:06:47.120 --> 00:06:49.040 align:middle line:84%
And of course, you'll
see exactly how

00:06:49.040 --> 00:06:51.240 align:middle line:84%
they're used during the
practical demonstration.

00:06:51.240 --> 00:06:54.110 align:middle line:84%
So coming down to the
actual exploitation

00:06:54.110 --> 00:06:57.770 align:middle line:84%
of this vulnerability, in order
to exploit this vulnerability,

00:06:57.770 --> 00:07:01.160 align:middle line:84%
you will need to locate an input
vector or script that allows

00:07:01.160 --> 00:07:02.480 align:middle line:90%
you to communicate with Bash.

00:07:02.480 --> 00:07:05.480 align:middle line:84%
That's really the crux
of this vulnerability.

00:07:05.480 --> 00:07:07.670 align:middle line:84%
Now, in the context of
an Apache web server,

00:07:07.670 --> 00:07:10.130 align:middle line:84%
we can utilize any
legitimate CGI scripts

00:07:10.130 --> 00:07:12.090 align:middle line:90%
accessible on the web server.

00:07:12.090 --> 00:07:14.810 align:middle line:84%
And because they are
interacting with Bash

00:07:14.810 --> 00:07:17.090 align:middle line:84%
or getting Bash to
execute some commands,

00:07:17.090 --> 00:07:22.040 align:middle line:84%
we can utilize or send a request
with this particular CGI script

00:07:22.040 --> 00:07:25.940 align:middle line:84%
and get those special
characters inputed as well as

00:07:25.940 --> 00:07:28.460 align:middle line:84%
any other commands that
we would like to execute.

00:07:28.460 --> 00:07:31.550 align:middle line:84%
So whenever a CGI
script is executed,

00:07:31.550 --> 00:07:33.920 align:middle line:84%
the web server will
initiate a new process

00:07:33.920 --> 00:07:36.020 align:middle line:84%
and run the CGI
script with Bash.

00:07:36.020 --> 00:07:40.520 align:middle line:84%
So whenever we make an HTTP
request for that particular CGI

00:07:40.520 --> 00:07:43.370 align:middle line:84%
script, the web server
will initiate a new process

00:07:43.370 --> 00:07:45.200 align:middle line:84%
and run the CGI
script with Bash.

00:07:45.200 --> 00:07:48.050 align:middle line:84%
So we can essentially input
the special characters

00:07:48.050 --> 00:07:49.940 align:middle line:84%
that I highlighted
in the previous slide

00:07:49.940 --> 00:07:53.240 align:middle line:90%
within one of the HTTP headers.

00:07:53.240 --> 00:07:57.500 align:middle line:84%
The most effective technique
is to actually input those

00:07:57.500 --> 00:07:59.840 align:middle line:84%
or inject those
parameters or characters

00:07:59.840 --> 00:08:02.390 align:middle line:84%
within the user-agent
HTTP header

00:08:02.390 --> 00:08:04.250 align:middle line:84%
and then specify
the other commands

00:08:04.250 --> 00:08:07.470 align:middle line:84%
that we would like to execute
after those characters.

00:08:07.470 --> 00:08:09.860 align:middle line:84%
So in terms of
exploitation, as I said,

00:08:09.860 --> 00:08:12.770 align:middle line:84%
we can do this both
manually and automatically.

00:08:12.770 --> 00:08:14.300 align:middle line:84%
Manually, this
can be done really

00:08:14.300 --> 00:08:17.570 align:middle line:90%
easily by the use of a proxy.

00:08:17.570 --> 00:08:20.060 align:middle line:90%
So we can use the Burp proxy.

00:08:20.060 --> 00:08:23.240 align:middle line:84%
And in terms of automating
this particular attack,

00:08:23.240 --> 00:08:26.090 align:middle line:84%
we can also utilize
an MSF exploit module.

00:08:26.090 --> 00:08:27.800 align:middle line:84%
And in both cases,
I'll be showing you

00:08:27.800 --> 00:08:30.680 align:middle line:84%
how to obtain a reverse shell
or a Meterpreter session,

00:08:30.680 --> 00:08:31.770 align:middle line:90%
respectively.

00:08:31.770 --> 00:08:32.270 align:middle line:90%
All right.

00:08:32.270 --> 00:08:35.179 align:middle line:84%
So now that we have an idea as
to what this vulnerability is

00:08:35.179 --> 00:08:37.640 align:middle line:84%
and how it can be
exploited, let's get

00:08:37.640 --> 00:08:39.440 align:middle line:84%
started with the
practical demonstration

00:08:39.440 --> 00:08:40.640 align:middle line:90%
side of this video.

00:08:40.640 --> 00:08:43.830 align:middle line:84%
And this video already has a
lab environment attached to it.

00:08:43.830 --> 00:08:46.280 align:middle line:84%
So you can start it up,
and you can follow along

00:08:46.280 --> 00:08:47.250 align:middle line:90%
with the techniques.

00:08:47.250 --> 00:08:49.310 align:middle line:84%
So I'm going to start
up my lab environment,

00:08:49.310 --> 00:08:53.500 align:middle line:84%
and I'll see you within
the lab environment.

00:08:53.500 --> 00:08:54.000 align:middle line:90%
All right.

00:08:54.000 --> 00:08:55.930 align:middle line:84%
So I'm back within
the lab environment.

00:08:55.930 --> 00:08:58.980 align:middle line:84%
And in this case, you will not
be provided with the target IP,

00:08:58.980 --> 00:09:02.670 align:middle line:84%
but that can easily be obtained
by opening up your terminal.

00:09:02.670 --> 00:09:05.260 align:middle line:84%
I'm just going to open
that up and maximize this,

00:09:05.260 --> 00:09:06.630 align:middle line:90%
so you can see what's going on.

00:09:06.630 --> 00:09:08.880 align:middle line:84%
If you type in ifconfig
and take a look

00:09:08.880 --> 00:09:11.160 align:middle line:84%
at the interface
Ethernet 1, this

00:09:11.160 --> 00:09:14.370 align:middle line:84%
is your IP address here or the
IP address of the Kali Linux

00:09:14.370 --> 00:09:15.510 align:middle line:90%
system.

00:09:15.510 --> 00:09:18.060 align:middle line:84%
The target IP address is
going to be the next IP

00:09:18.060 --> 00:09:19.450 align:middle line:90%
address within this subnet.

00:09:19.450 --> 00:09:21.090 align:middle line:84%
And of course, in
your case, the subnet

00:09:21.090 --> 00:09:22.410 align:middle line:90%
is going to be different.

00:09:22.410 --> 00:09:24.900 align:middle line:84%
All you need to do is
just change the 2 to a 3,

00:09:24.900 --> 00:09:26.590 align:middle line:90%
and that's the target IP.

00:09:26.590 --> 00:09:28.560 align:middle line:90%
So we'll just copy that there.

00:09:28.560 --> 00:09:31.260 align:middle line:84%
And I'm going to form an
Nmap scan on the target

00:09:31.260 --> 00:09:34.170 align:middle line:84%
to identify whether we have
an Apache web server running.

00:09:34.170 --> 00:09:37.140 align:middle line:84%
So I'm going to say nmap, and
we'll perform a service version

00:09:37.140 --> 00:09:38.310 align:middle line:90%
detection scan.

00:09:38.310 --> 00:09:41.790 align:middle line:84%
And I'll paste in the target
IP, so I'll change the 2 to a 3,

00:09:41.790 --> 00:09:43.070 align:middle line:90%
and I'll hit Enter.

00:09:43.070 --> 00:09:45.195 align:middle line:84%
And I'll give this a couple
of seconds to complete.

00:09:45.195 --> 00:09:48.920 align:middle line:90%


00:09:48.920 --> 00:09:49.420 align:middle line:90%
All right.

00:09:49.420 --> 00:09:51.350 align:middle line:90%
So the Nmap scan is complete.

00:09:51.350 --> 00:09:53.680 align:middle line:84%
And as you can see,
on port 80, the target

00:09:53.680 --> 00:09:56.260 align:middle line:90%
is running an Apache web server.

00:09:56.260 --> 00:09:57.940 align:middle line:90%
So we can actually confirm that.

00:09:57.940 --> 00:10:00.520 align:middle line:84%
I'm just going to copy the
target IP right over here.

00:10:00.520 --> 00:10:01.990 align:middle line:90%
I'm going to open up my browser.

00:10:01.990 --> 00:10:05.380 align:middle line:84%
And let's actually confirm
whether we have a website

00:10:05.380 --> 00:10:06.740 align:middle line:90%
or a web server running.

00:10:06.740 --> 00:10:07.465 align:middle line:90%
So there we are.

00:10:07.465 --> 00:10:08.470 align:middle line:90%
I'll hit Enter.

00:10:08.470 --> 00:10:09.760 align:middle line:90%
And as you can see--

00:10:09.760 --> 00:10:11.090 align:middle line:90%
let me just maximize this.

00:10:11.090 --> 00:10:14.090 align:middle line:84%
You can see that the website is
currently under construction.

00:10:14.090 --> 00:10:16.030 align:middle line:84%
However, if you pay
close attention,

00:10:16.030 --> 00:10:18.130 align:middle line:84%
there's a piece
of text here that

00:10:18.130 --> 00:10:20.500 align:middle line:84%
doesn't look to be
rendered in HTML

00:10:20.500 --> 00:10:24.310 align:middle line:84%
or doesn't seem to have any CSS
attributes associated with it.

00:10:24.310 --> 00:10:27.310 align:middle line:84%
And this essentially
tells us that the website

00:10:27.310 --> 00:10:31.030 align:middle line:84%
will be online in 0 days,
23 hours, and 57 minutes.

00:10:31.030 --> 00:10:33.070 align:middle line:90%
Really, really cool.

00:10:33.070 --> 00:10:35.200 align:middle line:84%
But how is this
being done because it

00:10:35.200 --> 00:10:37.450 align:middle line:84%
looks like it's very
dynamic, and it's

00:10:37.450 --> 00:10:38.890 align:middle line:90%
being done on the server side?

00:10:38.890 --> 00:10:41.950 align:middle line:84%
Well, this is being accomplished
through the use of a CGI

00:10:41.950 --> 00:10:42.680 align:middle line:90%
script.

00:10:42.680 --> 00:10:46.660 align:middle line:84%
So if we view the actual
source of this page

00:10:46.660 --> 00:10:50.008 align:middle line:84%
and take a look at where
that particular-- at where

00:10:50.008 --> 00:10:53.000 align:middle line:84%
that particular output
is being displayed,

00:10:53.000 --> 00:10:55.390 align:middle line:84%
you can see there's
some JavaScript here.

00:10:55.390 --> 00:11:00.040 align:middle line:84%
And we can see that it actually
executes a CGI script called

00:11:00.040 --> 00:11:02.080 align:middle line:90%
gettime.cgi.

00:11:02.080 --> 00:11:05.270 align:middle line:84%
And the CGI script is stored
in the root of the web server,

00:11:05.270 --> 00:11:06.890 align:middle line:90%
which means we can access it.

00:11:06.890 --> 00:11:08.600 align:middle line:90%
It's publicly accessible.

00:11:08.600 --> 00:11:10.260 align:middle line:90%
So we can say, gettime.cgi.

00:11:10.260 --> 00:11:13.650 align:middle line:90%


00:11:13.650 --> 00:11:14.150 align:middle line:90%
All right.

00:11:14.150 --> 00:11:16.760 align:middle line:84%
So and you can see, it just
displays the actual information

00:11:16.760 --> 00:11:18.530 align:middle line:90%
that we got on the website.

00:11:18.530 --> 00:11:21.020 align:middle line:84%
And that means that
the web server has

00:11:21.020 --> 00:11:23.060 align:middle line:90%
a CGI script that we can use.

00:11:23.060 --> 00:11:27.020 align:middle line:84%
And again, this CGI script is
parsing in commands to Bash

00:11:27.020 --> 00:11:29.150 align:middle line:84%
or is executing
commands with Bash.

00:11:29.150 --> 00:11:33.440 align:middle line:84%
And what we can do is utilize
this as our input vector.

00:11:33.440 --> 00:11:35.720 align:middle line:84%
However, we also
need to check as

00:11:35.720 --> 00:11:38.060 align:middle line:84%
to whether this
particular server

00:11:38.060 --> 00:11:39.950 align:middle line:84%
or whether this
particular system is

00:11:39.950 --> 00:11:43.760 align:middle line:84%
vulnerable to the Shellshock
attack or vulnerability.

00:11:43.760 --> 00:11:46.490 align:middle line:84%
And that can easily
be done with Nmap.

00:11:46.490 --> 00:11:49.910 align:middle line:84%
And the way we can do that is by
saying Nmap and then utilizing

00:11:49.910 --> 00:11:51.120 align:middle line:90%
an Nmap script.

00:11:51.120 --> 00:11:52.610 align:middle line:84%
So I'm going to
say nmap, and we're

00:11:52.610 --> 00:11:55.170 align:middle line:84%
going to perform service
version detection scan.

00:11:55.170 --> 00:11:56.930 align:middle line:90%
I'll paste in the target IP.

00:11:56.930 --> 00:12:00.690 align:middle line:84%
We're going to say script
equals, and in this case,

00:12:00.690 --> 00:12:04.260 align:middle line:84%
we're using the Shellshock
script, so shellshock.

00:12:04.260 --> 00:12:09.650 align:middle line:84%
And the actual name
here is HTTP shellshock.

00:12:09.650 --> 00:12:10.760 align:middle line:90%
There we are.

00:12:10.760 --> 00:12:13.220 align:middle line:84%
And then, we need to specify
the script arguments,

00:12:13.220 --> 00:12:15.950 align:middle line:84%
and the script arguments
for this particular script

00:12:15.950 --> 00:12:19.340 align:middle line:84%
are essentially utilized
to specify where

00:12:19.340 --> 00:12:21.800 align:middle line:84%
or the actual CGI script
that we're testing.

00:12:21.800 --> 00:12:23.840 align:middle line:84%
So I'm going to say
script arguments.

00:12:23.840 --> 00:12:27.560 align:middle line:84%
And then in double-quotes,
I'm going to say HTTP,

00:12:27.560 --> 00:12:33.080 align:middle line:84%
and these are the script
arguments, so http-shellshock.

00:12:33.080 --> 00:12:36.390 align:middle line:84%
There we are, and
then we specify

00:12:36.390 --> 00:12:42.070 align:middle line:84%
shellshock.uri to specify the
actual URI of the CGI script.

00:12:42.070 --> 00:12:44.885 align:middle line:84%
In this case, the CGI script
is under the root of the web

00:12:44.885 --> 00:12:49.290 align:middle line:84%
server, and the
name is gettime.cgi,

00:12:49.290 --> 00:12:52.560 align:middle line:84%
and we can then close the
actual quotation there.

00:12:52.560 --> 00:12:54.420 align:middle line:84%
And we can hit
Enter, and I'm just

00:12:54.420 --> 00:12:56.940 align:middle line:84%
going to wait for
this to complete.

00:12:56.940 --> 00:12:57.440 align:middle line:90%
All right.

00:12:57.440 --> 00:12:59.250 align:middle line:84%
The Nmap script
scan is complete.

00:12:59.250 --> 00:13:02.210 align:middle line:84%
And as you can see, it gives
us the basic information

00:13:02.210 --> 00:13:03.630 align:middle line:90%
we got previously.

00:13:03.630 --> 00:13:06.230 align:middle line:84%
However, the output for
the http-shellshock script

00:13:06.230 --> 00:13:08.300 align:middle line:84%
tells us that this
target is vulnerable.

00:13:08.300 --> 00:13:11.690 align:middle line:84%
So you can see http-shellshock
vulnerability state

00:13:11.690 --> 00:13:13.550 align:middle line:90%
is vulnerable and exploitable.

00:13:13.550 --> 00:13:17.060 align:middle line:84%
It provides you with the
actual CVE right over here.

00:13:17.060 --> 00:13:19.190 align:middle line:84%
And this web
application might be

00:13:19.190 --> 00:13:21.710 align:middle line:84%
affected by the vulnerability
known as Shellshock.

00:13:21.710 --> 00:13:24.590 align:middle line:84%
It seems the server is
executing commands injected

00:13:24.590 --> 00:13:26.910 align:middle line:90%
via malicious HTTP headers.

00:13:26.910 --> 00:13:27.410 align:middle line:90%
All right.

00:13:27.410 --> 00:13:33.230 align:middle line:84%
So that means we can utilize the
CGI script and inject our own--

00:13:33.230 --> 00:13:35.420 align:middle line:84%
we can essentially inject
the actual characters,

00:13:35.420 --> 00:13:38.720 align:middle line:84%
the special characters,
within HTTP headers.

00:13:38.720 --> 00:13:40.520 align:middle line:84%
And in this case, we
will be injecting them

00:13:40.520 --> 00:13:43.550 align:middle line:90%
in the actual user-agent header.

00:13:43.550 --> 00:13:45.620 align:middle line:84%
So in order to do this,
what we're going to do

00:13:45.620 --> 00:13:47.870 align:middle line:84%
is we are going to
open up the Burp proxy.

00:13:47.870 --> 00:13:51.020 align:middle line:84%
But before we do that, this
particular lab environment

00:13:51.020 --> 00:13:53.360 align:middle line:84%
has Mozilla Firefox
already configured

00:13:53.360 --> 00:13:55.400 align:middle line:84%
with FoxyProxy, which
is a plug-in that

00:13:55.400 --> 00:13:58.400 align:middle line:84%
allows you to automatically
switch between proxies.

00:13:58.400 --> 00:14:01.590 align:middle line:84%
And a Burp Suite profile has
already been created for you,

00:14:01.590 --> 00:14:02.765 align:middle line:90%
so just click on there.

00:14:02.765 --> 00:14:04.580 align:middle line:84%
That means that
all traffic will be

00:14:04.580 --> 00:14:07.040 align:middle line:90%
redirected to the Burp proxy.

00:14:07.040 --> 00:14:11.660 align:middle line:84%
We can then open up Burp Suite
by clicking on the Kali menu

00:14:11.660 --> 00:14:14.630 align:middle line:84%
and heading over to web
application analysis and Burp

00:14:14.630 --> 00:14:16.310 align:middle line:90%
Suite.

00:14:16.310 --> 00:14:18.500 align:middle line:84%
And we'll give this a couple
of seconds to start up.

00:14:18.500 --> 00:14:20.280 align:middle line:90%
This is a temporary project.

00:14:20.280 --> 00:14:24.750 align:middle line:84%
Next, we're just going to use
the default configuration.

00:14:24.750 --> 00:14:27.860 align:middle line:84%
And we're going to give this a
couple of seconds to start up.

00:14:27.860 --> 00:14:28.910 align:middle line:90%
All right.

00:14:28.910 --> 00:14:31.940 align:middle line:84%
Disregard the actual
message there.

00:14:31.940 --> 00:14:33.470 align:middle line:84%
And we're going
to click on Proxy

00:14:33.470 --> 00:14:35.780 align:middle line:84%
and make sure that
intercept is set to on.

00:14:35.780 --> 00:14:38.210 align:middle line:84%
I'm just going to afford
these requests here.

00:14:38.210 --> 00:14:41.270 align:middle line:84%
And then, we can request
or make a GET request

00:14:41.270 --> 00:14:43.620 align:middle line:90%
for the gettime.cgi script.

00:14:43.620 --> 00:14:45.050 align:middle line:90%
So I'm going to say reload.

00:14:45.050 --> 00:14:48.080 align:middle line:84%
And you can see it's going to
be intercepted within the proxy.

00:14:48.080 --> 00:14:49.790 align:middle line:84%
And as I said, we
are going to be

00:14:49.790 --> 00:14:53.960 align:middle line:84%
injecting the special characters
in the user-agent HTTP header.

00:14:53.960 --> 00:14:57.020 align:middle line:84%
In order to do this, we can
send this particular request

00:14:57.020 --> 00:14:58.670 align:middle line:90%
to the repeater.

00:14:58.670 --> 00:15:01.100 align:middle line:84%
And I'll then click
on the Repeater tab,

00:15:01.100 --> 00:15:04.490 align:middle line:84%
and we can get rid of the
user agent information here.

00:15:04.490 --> 00:15:07.280 align:middle line:84%
And we can replace
that with our own--

00:15:07.280 --> 00:15:08.720 align:middle line:90%
with the special characters.

00:15:08.720 --> 00:15:10.280 align:middle line:84%
And in order to do
this, we're just

00:15:10.280 --> 00:15:12.120 align:middle line:90%
going to paste or type them in.

00:15:12.120 --> 00:15:14.750 align:middle line:84%
So we start off
with two brackets,

00:15:14.750 --> 00:15:16.880 align:middle line:90%
and we then have curly braces.

00:15:16.880 --> 00:15:18.830 align:middle line:84%
And within the
curly braces, we are

00:15:18.830 --> 00:15:23.780 align:middle line:84%
going to specify that we
want a colon and semicolon.

00:15:23.780 --> 00:15:26.570 align:middle line:84%
And then we're going to
close the curly braces.

00:15:26.570 --> 00:15:30.890 align:middle line:84%
And we're then going to
specify another semicolon,

00:15:30.890 --> 00:15:33.167 align:middle line:84%
and then we're
going to say echo.

00:15:33.167 --> 00:15:35.000 align:middle line:84%
I'm just going to type
that in correctly, so

00:15:35.000 --> 00:15:40.760 align:middle line:84%
echo and echo, again, so echo
semicolon, echo semicolon.

00:15:40.760 --> 00:15:43.020 align:middle line:84%
And then we can execute
our own commands.

00:15:43.020 --> 00:15:45.650 align:middle line:90%
So we can say /bin/bash -c.

00:15:45.650 --> 00:15:47.600 align:middle line:84%
And in this case,
let's try and print

00:15:47.600 --> 00:15:50.420 align:middle line:84%
out the contents of the password
file on the Linux system.

00:15:50.420 --> 00:15:52.710 align:middle line:84%
Of course, you can
execute other commands.

00:15:52.710 --> 00:15:55.688 align:middle line:84%
So I'll just say
cat /etc/passwd.

00:15:55.688 --> 00:15:57.980 align:middle line:84%
And let's see whether we can
enumerate that information

00:15:57.980 --> 00:15:59.940 align:middle line:84%
and test whether
this actually works.

00:15:59.940 --> 00:16:03.890 align:middle line:84%
So to actually send that
request with a repeater,

00:16:03.890 --> 00:16:06.810 align:middle line:84%
let me just expand
the window here.

00:16:06.810 --> 00:16:09.630 align:middle line:84%
We can just say
send, and you can

00:16:09.630 --> 00:16:12.120 align:middle line:84%
see that this will
actually display

00:16:12.120 --> 00:16:13.360 align:middle line:90%
the output of that command.

00:16:13.360 --> 00:16:15.510 align:middle line:84%
So I'm just going to
open up Burp again here,

00:16:15.510 --> 00:16:16.780 align:middle line:90%
and there we are.

00:16:16.780 --> 00:16:19.350 align:middle line:84%
So you can see that we
specify we wanted to access

00:16:19.350 --> 00:16:21.640 align:middle line:84%
the contents of the
file cat /etc/passwd.

00:16:21.640 --> 00:16:23.550 align:middle line:84%
And you can see
that is executed,

00:16:23.550 --> 00:16:25.390 align:middle line:84%
and we get the output
right over here.

00:16:25.390 --> 00:16:27.870 align:middle line:84%
So the password file
on Linux essentially

00:16:27.870 --> 00:16:30.250 align:middle line:84%
contains a list of
all user accounts.

00:16:30.250 --> 00:16:33.180 align:middle line:84%
So it looks like we have
a syslog account, a nobody

00:16:33.180 --> 00:16:36.630 align:middle line:84%
account, as well as
a backup account,

00:16:36.630 --> 00:16:38.650 align:middle line:84%
and the root account
right over there.

00:16:38.650 --> 00:16:39.150 align:middle line:90%
All right.

00:16:39.150 --> 00:16:42.270 align:middle line:84%
So that essentially verifies
that this vulnerability

00:16:42.270 --> 00:16:43.530 align:middle line:90%
does indeed work.

00:16:43.530 --> 00:16:46.660 align:middle line:84%
Now, what if we wanted to gain
a reverse shell on the target

00:16:46.660 --> 00:16:47.160 align:middle line:90%
system?

00:16:47.160 --> 00:16:48.580 align:middle line:84%
How would we go
about doing that?

00:16:48.580 --> 00:16:51.900 align:middle line:84%
Well, we can utilize Bash
to essentially connect

00:16:51.900 --> 00:16:54.435 align:middle line:84%
to a listener on our
Kali Linux system.

00:16:54.435 --> 00:16:56.310 align:middle line:84%
So in order to do that,
we're going to set up

00:16:56.310 --> 00:16:57.780 align:middle line:90%
a listener with Netcat.

00:16:57.780 --> 00:17:00.300 align:middle line:84%
So I'm going to
say Netcat -nvlp.

00:17:00.300 --> 00:17:02.820 align:middle line:84%
And I'm going to
listen on port 1234.

00:17:02.820 --> 00:17:04.380 align:middle line:84%
I'm going to Enter,
and it's going

00:17:04.380 --> 00:17:08.280 align:middle line:84%
to listen on that port for the
connection when it is executed

00:17:08.280 --> 00:17:10.589 align:middle line:84%
or when a connection is
made from the target system.

00:17:10.589 --> 00:17:12.540 align:middle line:84%
I'm then going to
open up Burp Suite.

00:17:12.540 --> 00:17:17.490 align:middle line:84%
And within this particular--
within the request field here--

00:17:17.490 --> 00:17:21.510 align:middle line:84%
let me see if I can actually
zoom in here, so Burp.

00:17:21.510 --> 00:17:23.680 align:middle line:90%
I'm just going to zoom in.

00:17:23.680 --> 00:17:24.180 align:middle line:90%
All right.

00:17:24.180 --> 00:17:26.222 align:middle line:84%
So I've been able to zoom
in, so you can actually

00:17:26.222 --> 00:17:27.520 align:middle line:90%
see what's going on here.

00:17:27.520 --> 00:17:30.120 align:middle line:84%
And you can see that
this was the command

00:17:30.120 --> 00:17:32.160 align:middle line:90%
that we specified earlier on.

00:17:32.160 --> 00:17:34.470 align:middle line:84%
And what we're going
to do is we are just

00:17:34.470 --> 00:17:36.850 align:middle line:84%
going to replace this
particular command here

00:17:36.850 --> 00:17:39.060 align:middle line:84%
because we are going
to be connecting

00:17:39.060 --> 00:17:41.200 align:middle line:90%
with Bash to our listener.

00:17:41.200 --> 00:17:45.870 align:middle line:84%
And in order to do this, we
are going to say bash -i.

00:17:45.870 --> 00:17:48.060 align:middle line:84%
And we are going
to connect, so I'm

00:17:48.060 --> 00:17:51.360 align:middle line:84%
going to just output this
or redirect the output.

00:17:51.360 --> 00:17:59.250 align:middle line:84%
And we are then going to utilize
the dev/tcp binary, so dev/tcp.

00:17:59.250 --> 00:18:02.505 align:middle line:84%
And then we need to specify
our Kali Linux IP and of--

00:18:02.505 --> 00:18:04.630 align:middle line:84%
remember, in your case,
it's going to be different.

00:18:04.630 --> 00:18:07.920 align:middle line:84%
So I'll open up a new tab
here, and I'll say ifconfig,

00:18:07.920 --> 00:18:10.470 align:middle line:84%
and your IP address is
going to be the IP attached

00:18:10.470 --> 00:18:12.620 align:middle line:90%
to the interface Ethernet 1.

00:18:12.620 --> 00:18:13.200 align:middle line:90%
All right.

00:18:13.200 --> 00:18:18.060 align:middle line:84%
So I'll go back into Burp,
and I'll paste that in there.

00:18:18.060 --> 00:18:20.948 align:middle line:84%
And let me just make sure that
that is formatted correctly.

00:18:20.948 --> 00:18:21.490 align:middle line:90%
There we are.

00:18:21.490 --> 00:18:24.420 align:middle line:84%
And then, I need to specify the
port that we're connecting to

00:18:24.420 --> 00:18:26.010 align:middle line:90%
on our Kali Linux system.

00:18:26.010 --> 00:18:30.030 align:middle line:84%
In this case, it's
port 1234, and then we

00:18:30.030 --> 00:18:35.170 align:middle line:84%
are just going to say 0
redirect the output and 1.

00:18:35.170 --> 00:18:35.930 align:middle line:90%
There we are.

00:18:35.930 --> 00:18:40.490 align:middle line:84%
And we can essentially
just hit Forward or Send,

00:18:40.490 --> 00:18:44.060 align:middle line:84%
and we should get a reverse
shell on our Netcat listener,

00:18:44.060 --> 00:18:44.870 align:middle line:90%
and we do.

00:18:44.870 --> 00:18:47.450 align:middle line:84%
So you can see we get a
connection from the target,

00:18:47.450 --> 00:18:51.260 align:middle line:84%
and we're currently logged on
as the daemon user @victim-1.

00:18:51.260 --> 00:18:53.150 align:middle line:90%
So I can say, who am I?

00:18:53.150 --> 00:18:55.610 align:middle line:84%
And I can also enumerate
the information

00:18:55.610 --> 00:18:57.210 align:middle line:90%
regarding the distribution.

00:18:57.210 --> 00:19:01.200 align:middle line:84%
So I can say cat /etc/*issue
or cat /etc/*release.

00:19:01.200 --> 00:19:04.970 align:middle line:84%
So you can see, we're
running Ubuntu 14.04.6.

00:19:04.970 --> 00:19:06.935 align:middle line:90%
And uname -a.

00:19:06.935 --> 00:19:07.970 align:middle line:90%
All right, and we are.

00:19:07.970 --> 00:19:10.830 align:middle line:84%
So you can see that gives
you the kernel information,

00:19:10.830 --> 00:19:11.760 align:middle line:90%
et cetera, et cetera.

00:19:11.760 --> 00:19:12.260 align:middle line:90%
All right.

00:19:12.260 --> 00:19:15.950 align:middle line:84%
So that is how to exploit the
vulnerability manually using

00:19:15.950 --> 00:19:17.210 align:middle line:90%
the Burp proxy.

00:19:17.210 --> 00:19:19.310 align:middle line:84%
What we're now going
to do is take a look

00:19:19.310 --> 00:19:21.590 align:middle line:84%
at how to exploit
this vulnerability

00:19:21.590 --> 00:19:23.700 align:middle line:90%
with the Metasploit framework.

00:19:23.700 --> 00:19:25.710 align:middle line:84%
So I'm just going to
open up a new tab here.

00:19:25.710 --> 00:19:29.570 align:middle line:84%
And we'll start up the
PostgreSQL Database Service.

00:19:29.570 --> 00:19:33.060 align:middle line:84%
And I'm also going to
start up MSF console,

00:19:33.060 --> 00:19:36.560 align:middle line:84%
and we'll give this a couple
of seconds to start up.

00:19:36.560 --> 00:19:37.060 align:middle line:90%
All right.

00:19:37.060 --> 00:19:38.350 align:middle line:90%
So that is started up.

00:19:38.350 --> 00:19:41.270 align:middle line:84%
And we can search for the actual
name of the vulnerability.

00:19:41.270 --> 00:19:43.960 align:middle line:84%
So I can say
shellshock, and we have

00:19:43.960 --> 00:19:46.220 align:middle line:90%
two modules that we can use.

00:19:46.220 --> 00:19:48.520 align:middle line:84%
First of all, we have the
auxiliary module here.

00:19:48.520 --> 00:19:51.020 align:middle line:90%
I'm just going to zoom out.

00:19:51.020 --> 00:19:53.750 align:middle line:84%
So let me just zoom out here,
so you can actually see that.

00:19:53.750 --> 00:19:55.300 align:middle line:84%
So we have the
auxiliary module which

00:19:55.300 --> 00:19:58.580 align:middle line:84%
will tell you whether the
target server is vulnerable.

00:19:58.580 --> 00:20:02.150 align:middle line:84%
And then we have the exploit
module right over here.

00:20:02.150 --> 00:20:02.930 align:middle line:90%
All right.

00:20:02.930 --> 00:20:07.180 align:middle line:84%
And I'm just going to copy
that there, use, and paste.

00:20:07.180 --> 00:20:07.680 align:middle line:90%
All right.

00:20:07.680 --> 00:20:10.320 align:middle line:84%
So you can see Apache
mode CGI Bash environment

00:20:10.320 --> 00:20:12.810 align:middle line:90%
executable or execution.

00:20:12.810 --> 00:20:14.280 align:middle line:84%
And then, we can
clear the terminal

00:20:14.280 --> 00:20:17.070 align:middle line:90%
and show the options here.

00:20:17.070 --> 00:20:19.650 align:middle line:84%
And in terms of the options
that you need to specify,

00:20:19.650 --> 00:20:22.290 align:middle line:84%
you need to specify
the target or rather

00:20:22.290 --> 00:20:24.810 align:middle line:84%
the target IP address
as well as the port

00:20:24.810 --> 00:20:26.550 align:middle line:84%
that the web server
is listening on.

00:20:26.550 --> 00:20:28.740 align:middle line:84%
In this case, it's port
80, so that's fine.

00:20:28.740 --> 00:20:32.592 align:middle line:84%
So ideally, we only need
to specify the target IP,

00:20:32.592 --> 00:20:34.050 align:middle line:84%
which, in this
case, I'm just going

00:20:34.050 --> 00:20:35.670 align:middle line:90%
to copy from my web browser.

00:20:35.670 --> 00:20:37.510 align:middle line:90%
That is right over here.

00:20:37.510 --> 00:20:39.430 align:middle line:90%
So I'll just copy that there.

00:20:39.430 --> 00:20:41.670 align:middle line:84%
And what I'll do is
I'll just disable

00:20:41.670 --> 00:20:45.360 align:middle line:84%
or get rid of Burp Suite right
now because we don't need it.

00:20:45.360 --> 00:20:47.970 align:middle line:84%
There we are, and I'll also
disable the Burp Proxy,

00:20:47.970 --> 00:20:48.870 align:middle line:90%
so turn off.

00:20:48.870 --> 00:20:52.870 align:middle line:84%
And you can see we can still
request for that CGI script.

00:20:52.870 --> 00:20:57.240 align:middle line:84%
So I'm going to say set
RHOSTS to the target IP.

00:20:57.240 --> 00:21:01.050 align:middle line:84%
And I'm just going to get
rid of the HTTP option there,

00:21:01.050 --> 00:21:03.400 align:middle line:90%
and I'll hit Enter.

00:21:03.400 --> 00:21:06.160 align:middle line:84%
And we then need to
specify the target URI.

00:21:06.160 --> 00:21:08.780 align:middle line:84%
That is essentially the
path to the CGI script.

00:21:08.780 --> 00:21:16.088 align:middle line:84%
So I'll say set, and we're
going to say TARGETURI,

00:21:16.088 --> 00:21:17.880 align:middle line:84%
and we're going to set
that to gettime.cgi.

00:21:17.880 --> 00:21:20.790 align:middle line:90%


00:21:20.790 --> 00:21:21.290 align:middle line:90%
All right.

00:21:21.290 --> 00:21:23.450 align:middle line:84%
So once that's configured,
I can hit Exploit.

00:21:23.450 --> 00:21:26.610 align:middle line:90%


00:21:26.610 --> 00:21:27.190 align:middle line:90%
There we are.

00:21:27.190 --> 00:21:29.940 align:middle line:84%
Looks like it works, and we
get a Meterpreter session

00:21:29.940 --> 00:21:31.450 align:middle line:90%
on the target system.

00:21:31.450 --> 00:21:33.160 align:middle line:90%
So again, sysinfo.

00:21:33.160 --> 00:21:34.950 align:middle line:84%
We'll pretty much
get exactly what

00:21:34.950 --> 00:21:37.140 align:middle line:90%
we got on our reverse shell.

00:21:37.140 --> 00:21:37.950 align:middle line:90%
So there we are.

00:21:37.950 --> 00:21:42.270 align:middle line:84%
It's running Ubuntu 14.04,
and you now have access

00:21:42.270 --> 00:21:43.230 align:middle line:90%
to the target system.

00:21:43.230 --> 00:21:45.240 align:middle line:84%
And of course, the
next logical step

00:21:45.240 --> 00:21:47.010 align:middle line:84%
would be to elevate
your privileges.

00:21:47.010 --> 00:21:49.390 align:middle line:84%
But we'll get there
when we get there.

00:21:49.390 --> 00:21:52.140 align:middle line:84%
So this is going to conclude
the practical demonstration

00:21:52.140 --> 00:21:55.150 align:middle line:90%
side of this video.

00:21:55.150 --> 00:21:57.510 align:middle line:84%
In the next video, we
will be taking a look

00:21:57.510 --> 00:22:01.080 align:middle line:84%
at how we can exploit
FTP, or rather, a Linux

00:22:01.080 --> 00:22:02.860 align:middle line:90%
server running FTP.

00:22:02.860 --> 00:22:03.360 align:middle line:90%
All right.

00:22:03.360 --> 00:22:06.530 align:middle line:84%
So I'll see you
in the next video.

00:22:06.530 --> 00:22:08.043 align:middle line:90%