WEBVTT

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


00:00:03.388 --> 00:00:06.776 align:middle line:90%
[MUSIC PLAYING]

00:00:06.776 --> 00:00:10.170 align:middle line:90%


00:00:10.170 --> 00:00:11.790 align:middle line:90%
Exploiting Samba.

00:00:11.790 --> 00:00:14.250 align:middle line:84%
In this video, we are
going to be exploring

00:00:14.250 --> 00:00:18.390 align:middle line:84%
the process of exploiting the
Linux implementation of SMB,

00:00:18.390 --> 00:00:19.530 align:middle line:90%
which is Samba.

00:00:19.530 --> 00:00:23.230 align:middle line:84%
Now, during the enumeration
section of this course,

00:00:23.230 --> 00:00:26.700 align:middle line:84%
we explore the process of
performing SMB enumeration,

00:00:26.700 --> 00:00:30.210 align:middle line:84%
more specifically performing
enumeration on Samba.

00:00:30.210 --> 00:00:33.250 align:middle line:84%
So you should be familiar
with what Samba is.

00:00:33.250 --> 00:00:34.680 align:middle line:84%
However, if you're
not, I'm going

00:00:34.680 --> 00:00:38.820 align:middle line:84%
to give you a basic or brief
introduction to SMB and Samba.

00:00:38.820 --> 00:00:42.090 align:middle line:84%
So SMB stands for the
Server Message Block,

00:00:42.090 --> 00:00:44.250 align:middle line:84%
and it is a network
and file sharing

00:00:44.250 --> 00:00:47.490 align:middle line:84%
protocol that is used to
facilitate the sharing of files

00:00:47.490 --> 00:00:51.030 align:middle line:84%
and peripherals between
computers on a local network,

00:00:51.030 --> 00:00:52.680 align:middle line:90%
also known as a LAN.

00:00:52.680 --> 00:00:55.420 align:middle line:84%
So if you've ever worked
within a Windows environment,

00:00:55.420 --> 00:00:57.630 align:middle line:84%
then you should be
familiar with SMB.

00:00:57.630 --> 00:01:02.190 align:middle line:84%
SMB is used to share files or
to create shares on a system,

00:01:02.190 --> 00:01:04.620 align:middle line:84%
and then those shares can
be accessed by other Windows

00:01:04.620 --> 00:01:07.650 align:middle line:84%
systems within that
local area network.

00:01:07.650 --> 00:01:14.130 align:middle line:84%
So SMB utilizes port 445 on
TCP or rather the TCP port 445

00:01:14.130 --> 00:01:18.840 align:middle line:84%
by default. However, originally,
SMB ran on top of NetBIOS

00:01:18.840 --> 00:01:20.880 align:middle line:90%
using port 139.

00:01:20.880 --> 00:01:23.610 align:middle line:84%
So that begs the
question, what is Samba?

00:01:23.610 --> 00:01:26.940 align:middle line:84%
Well, Samba is the Linux
implementation of SMB

00:01:26.940 --> 00:01:30.090 align:middle line:84%
and essentially allows Windows
systems to access Linux shares

00:01:30.090 --> 00:01:32.050 align:middle line:90%
and devices, and vice versa.

00:01:32.050 --> 00:01:34.410 align:middle line:90%
So that's really what Samba is.

00:01:34.410 --> 00:01:36.870 align:middle line:84%
It's essentially
SMB but for Linux.

00:01:36.870 --> 00:01:40.030 align:middle line:84%
And during the Windows
exploitation section,

00:01:40.030 --> 00:01:43.200 align:middle line:84%
we explored the process of
exploiting SMB on Windows

00:01:43.200 --> 00:01:47.730 align:middle line:84%
through the EternalBlue exploit
or by exploiting the MS17-010

00:01:47.730 --> 00:01:48.908 align:middle line:90%
vulnerability.

00:01:48.908 --> 00:01:50.700 align:middle line:84%
It's going to be pretty
much the same thing

00:01:50.700 --> 00:01:54.030 align:middle line:84%
here, where we are exploiting
an inherent vulnerability

00:01:54.030 --> 00:01:54.900 align:middle line:90%
within Samba.

00:01:54.900 --> 00:01:58.560 align:middle line:84%
So we're not looking for
a misconfigured Samba

00:01:58.560 --> 00:02:00.990 align:middle line:84%
server or a misconfigured
Samba service that's

00:02:00.990 --> 00:02:02.070 align:middle line:90%
running on a target.

00:02:02.070 --> 00:02:06.060 align:middle line:84%
Instead, we are going to be
targeting a vulnerability that

00:02:06.060 --> 00:02:10.259 align:middle line:84%
again in this case can be found
within Samba version 3.5.0.

00:02:10.259 --> 00:02:14.430 align:middle line:84%
So Samba version 3.5.0 is
vulnerable to a remote code

00:02:14.430 --> 00:02:16.860 align:middle line:84%
execution vulnerability,
which allows

00:02:16.860 --> 00:02:19.020 align:middle line:84%
a malicious client
or an attacker

00:02:19.020 --> 00:02:22.140 align:middle line:84%
to upload a shared library
to a writable share

00:02:22.140 --> 00:02:24.760 align:middle line:84%
and then cause the server
to load and execute it.

00:02:24.760 --> 00:02:28.350 align:middle line:84%
So a shared library is pretty
much the Linux equivalent

00:02:28.350 --> 00:02:29.970 align:middle line:90%
of a DLL file.

00:02:29.970 --> 00:02:31.710 align:middle line:84%
So they're essentially
libraries that

00:02:31.710 --> 00:02:33.870 align:middle line:84%
are called upon by
services or programs.

00:02:33.870 --> 00:02:35.637 align:middle line:84%
And in this case,
what we're doing--

00:02:35.637 --> 00:02:37.470 align:middle line:84%
and of course, we are
going to be doing this

00:02:37.470 --> 00:02:40.080 align:middle line:84%
through a Metasploit
framework exploit module.

00:02:40.080 --> 00:02:41.940 align:middle line:84%
What we're doing here
is we're essentially

00:02:41.940 --> 00:02:44.550 align:middle line:84%
connecting to Samba
on the Linux target

00:02:44.550 --> 00:02:46.620 align:middle line:84%
and then uploading
a malicious shared

00:02:46.620 --> 00:02:48.630 align:middle line:84%
library that will
consequently provide us

00:02:48.630 --> 00:02:50.260 align:middle line:90%
with a command shell.

00:02:50.260 --> 00:02:52.770 align:middle line:84%
And again, we'll take a look
at how to upgrade that command

00:02:52.770 --> 00:02:54.330 align:middle line:90%
shell to interpret the session.

00:02:54.330 --> 00:02:58.350 align:middle line:84%
And of course, once
the actual Samba server

00:02:58.350 --> 00:03:00.940 align:middle line:84%
loads it and executes it,
we are going to get access.

00:03:00.940 --> 00:03:04.560 align:middle line:84%
So it's a really fairly
simple exploit to understand.

00:03:04.560 --> 00:03:08.490 align:middle line:84%
And it works very similarly to
the actual EternalBlue exploit.

00:03:08.490 --> 00:03:11.400 align:middle line:84%
In that, we are exploiting
an inherent vulnerability,

00:03:11.400 --> 00:03:14.800 align:middle line:84%
not an SMB or a Samba
misconfiguration.

00:03:14.800 --> 00:03:15.300 align:middle line:90%
All right.

00:03:15.300 --> 00:03:17.340 align:middle line:84%
So the lab environment
in this case

00:03:17.340 --> 00:03:20.250 align:middle line:84%
will allow us to showcase
or to demonstrate this.

00:03:20.250 --> 00:03:22.440 align:middle line:84%
And again, all you need
to do is just start up

00:03:22.440 --> 00:03:24.850 align:middle line:84%
your lab environment, and
you can then follow along.

00:03:24.850 --> 00:03:29.360 align:middle line:84%
So I'll see you within
the lab environment.

00:03:29.360 --> 00:03:29.860 align:middle line:90%
All right.

00:03:29.860 --> 00:03:32.030 align:middle line:84%
So I'm back within
the lab environment.

00:03:32.030 --> 00:03:34.810 align:middle line:84%
And the first step or the
first thing we need to do

00:03:34.810 --> 00:03:37.600 align:middle line:84%
is of course identify the
target IP address, which can

00:03:37.600 --> 00:03:39.820 align:middle line:90%
be done by typing in ifconfig.

00:03:39.820 --> 00:03:42.760 align:middle line:84%
And you want to look for
the Ethernet one interface.

00:03:42.760 --> 00:03:45.430 align:middle line:84%
And this is the IP address
of our current system

00:03:45.430 --> 00:03:48.520 align:middle line:84%
or the Kali Linux VM or
the Kali Linux instance

00:03:48.520 --> 00:03:50.140 align:middle line:90%
that we're currently utilizing.

00:03:50.140 --> 00:03:52.870 align:middle line:84%
And the target IP address
or the target system

00:03:52.870 --> 00:03:54.760 align:middle line:84%
is going to be on
the same subnet.

00:03:54.760 --> 00:03:57.010 align:middle line:84%
Now, the subnet of
course in your case

00:03:57.010 --> 00:04:00.970 align:middle line:84%
will change based on region,
but the target IP address

00:04:00.970 --> 00:04:04.060 align:middle line:84%
is always going to be the
next host or the next IP

00:04:04.060 --> 00:04:05.480 align:middle line:90%
address within this subnet.

00:04:05.480 --> 00:04:09.050 align:middle line:84%
So if our Kali Linux
system or instance

00:04:09.050 --> 00:04:15.035 align:middle line:84%
has an IP address
of 192.18.76.2,

00:04:15.035 --> 00:04:16.660 align:middle line:84%
then our target system
is going to have

00:04:16.660 --> 00:04:20.230 align:middle line:90%
an IP address of 192.18.76.3.

00:04:20.230 --> 00:04:23.620 align:middle line:84%
So it's always going to be the
third or the next IP address

00:04:23.620 --> 00:04:25.550 align:middle line:90%
within this particular subnet.

00:04:25.550 --> 00:04:26.800 align:middle line:90%
So I'm going to copy that.

00:04:26.800 --> 00:04:30.520 align:middle line:84%
We then want to start up
the PostgreSQL service

00:04:30.520 --> 00:04:33.940 align:middle line:84%
so that we can interact with the
Metasploit framework database.

00:04:33.940 --> 00:04:36.550 align:middle line:84%
I'm going to say
start, hit Enter.

00:04:36.550 --> 00:04:38.530 align:middle line:84%
We're going to give
that a few seconds.

00:04:38.530 --> 00:04:42.958 align:middle line:84%
We're then going to launch
MSF console, which is also

00:04:42.958 --> 00:04:44.125 align:middle line:90%
going to take a few seconds.

00:04:44.125 --> 00:04:50.090 align:middle line:90%


00:04:50.090 --> 00:04:52.070 align:middle line:84%
We're then going to
create a workspace

00:04:52.070 --> 00:04:55.020 align:middle line:90%
for our work or our assessment.

00:04:55.020 --> 00:04:57.380 align:middle line:84%
And we're going
to call it Samba.

00:04:57.380 --> 00:04:58.010 align:middle line:90%
All right.

00:04:58.010 --> 00:05:00.960 align:middle line:84%
And we're then going to set the
global variable for the Rhosts

00:05:00.960 --> 00:05:01.460 align:middle line:90%
option.

00:05:01.460 --> 00:05:03.002 align:middle line:84%
And we're going to
specify the target

00:05:03.002 --> 00:05:07.910 align:middle line:84%
IP, so make sure to change
the 2 into a 3 in your case.

00:05:07.910 --> 00:05:11.150 align:middle line:84%
The global variable option
here will essentially

00:05:11.150 --> 00:05:15.530 align:middle line:84%
save us from manually or
continually entering the target

00:05:15.530 --> 00:05:18.990 align:middle line:84%
IP whenever we load a new
module, which is very helpful.

00:05:18.990 --> 00:05:21.530 align:middle line:84%
So we're setting up the
global variable there.

00:05:21.530 --> 00:05:24.290 align:middle line:84%
The next step of course
is to perform an Nmap scan

00:05:24.290 --> 00:05:27.080 align:middle line:84%
on the target to identify
what version of Samba

00:05:27.080 --> 00:05:28.400 align:middle line:90%
is running on the target.

00:05:28.400 --> 00:05:33.890 align:middle line:84%
We can do this by utilizing the
DB Nmap command, which again

00:05:33.890 --> 00:05:37.610 align:middle line:84%
is pretty much will allow
us to perform an Nmap

00:05:37.610 --> 00:05:40.310 align:middle line:84%
scan from within the
Metasploit framework console

00:05:40.310 --> 00:05:42.980 align:middle line:84%
and consequently save the
results into the Metasploit

00:05:42.980 --> 00:05:44.258 align:middle line:90%
framework database.

00:05:44.258 --> 00:05:45.800 align:middle line:84%
So in this case,
I'm going to perform

00:05:45.800 --> 00:05:48.900 align:middle line:84%
a SYN scan and a
service detection scan,

00:05:48.900 --> 00:05:51.690 align:middle line:84%
as well as an operating
system detection scan.

00:05:51.690 --> 00:05:54.800 align:middle line:84%
So that is denoted
by SS, SV, and O.

00:05:54.800 --> 00:05:57.120 align:middle line:84%
We then paste in the
target IP address.

00:05:57.120 --> 00:06:00.170 align:middle line:84%
Of course, make sure
to change that to a 3.

00:06:00.170 --> 00:06:02.130 align:middle line:90%
And we start the Nmap scan.

00:06:02.130 --> 00:06:06.320 align:middle line:84%
So you want to give that a few
seconds to a couple of minutes.

00:06:06.320 --> 00:06:06.820 align:middle line:90%
All right.

00:06:06.820 --> 00:06:08.410 align:middle line:90%
So the Nmap scan completes.

00:06:08.410 --> 00:06:11.110 align:middle line:84%
And as you can see, the
target is running SMB

00:06:11.110 --> 00:06:13.090 align:middle line:90%
or has the SMB port open.

00:06:13.090 --> 00:06:15.880 align:middle line:84%
And the service version
of SMB is Samba,

00:06:15.880 --> 00:06:17.770 align:middle line:84%
but it doesn't give
us the exact version.

00:06:17.770 --> 00:06:20.050 align:middle line:84%
We only get a rough
estimate, which

00:06:20.050 --> 00:06:23.680 align:middle line:84%
in this case what Nmap
tells us is that it's either

00:06:23.680 --> 00:06:28.990 align:middle line:84%
running Samba version
3.X to 4.X, so anything

00:06:28.990 --> 00:06:32.620 align:middle line:84%
in between this, which in our
case, we can actually check.

00:06:32.620 --> 00:06:35.020 align:middle line:84%
And of course, we can
see that SMB is also

00:06:35.020 --> 00:06:38.320 align:middle line:84%
running on port 139
facilitated by NetBIOS,

00:06:38.320 --> 00:06:40.730 align:middle line:90%
which is again perfectly fine.

00:06:40.730 --> 00:06:44.450 align:middle line:84%
So what we can do now is of
course run a quick search.

00:06:44.450 --> 00:06:47.710 align:middle line:84%
And in this case, we are going
to again limit our search

00:06:47.710 --> 00:06:49.960 align:middle line:90%
results to the exploit modules.

00:06:49.960 --> 00:06:53.660 align:middle line:84%
And then for the name, we
are just going to say Samba.

00:06:53.660 --> 00:06:54.160 align:middle line:90%
All right.

00:06:54.160 --> 00:06:56.620 align:middle line:84%
And the exploit module
that we want to utilize

00:06:56.620 --> 00:07:01.390 align:middle line:84%
is the exploit Linux Samba is
known pipename exploit module.

00:07:01.390 --> 00:07:04.090 align:middle line:84%
As you can see, the rank is
set to excellent, which means

00:07:04.090 --> 00:07:06.490 align:middle line:90%
it works without any issues.

00:07:06.490 --> 00:07:08.410 align:middle line:84%
And as you can see,
this is the Samba

00:07:08.410 --> 00:07:11.200 align:middle line:84%
is known pipename
arbitrary module load.

00:07:11.200 --> 00:07:13.560 align:middle line:84%
So that's the exact module
that we want to use.

00:07:13.560 --> 00:07:14.830 align:middle line:90%
So I'm going to copy that.

00:07:14.830 --> 00:07:18.160 align:middle line:84%
And we're going to say use and
paste in the module name there.

00:07:18.160 --> 00:07:21.070 align:middle line:84%
If we show the
options here, you can

00:07:21.070 --> 00:07:23.020 align:middle line:84%
see that we need to
set up the target IP

00:07:23.020 --> 00:07:26.410 align:middle line:84%
address and the target SMB
port, which is set correctly.

00:07:26.410 --> 00:07:28.450 align:middle line:84%
In this case, we don't
need to set a payload

00:07:28.450 --> 00:07:30.980 align:middle line:84%
because it already has
a payload configured.

00:07:30.980 --> 00:07:34.360 align:middle line:84%
However, we will need to
actually configure or upgrade

00:07:34.360 --> 00:07:37.240 align:middle line:84%
our command shell into a
meterpreter session, which

00:07:37.240 --> 00:07:40.820 align:middle line:84%
we can do really easily as we
explored in the previous video.

00:07:40.820 --> 00:07:43.000 align:middle line:84%
We can also provide
the SMB folder,

00:07:43.000 --> 00:07:46.030 align:middle line:84%
which again allows us to
specify the directory to use

00:07:46.030 --> 00:07:48.070 align:middle line:90%
within the writable SMB share.

00:07:48.070 --> 00:07:50.620 align:middle line:84%
In our case, we
have no idea or we

00:07:50.620 --> 00:07:52.870 align:middle line:84%
haven't enumerated any
information regarding

00:07:52.870 --> 00:07:56.260 align:middle line:84%
the actual SMB folders or
the share names that contains

00:07:56.260 --> 00:07:57.760 align:middle line:90%
the writable directory.

00:07:57.760 --> 00:08:01.060 align:middle line:84%
So all we need to do in this
case is first of all run

00:08:01.060 --> 00:08:03.550 align:middle line:84%
the check command, which
will actually check

00:08:03.550 --> 00:08:05.020 align:middle line:90%
if the target is vulnerable.

00:08:05.020 --> 00:08:10.270 align:middle line:84%
And in this case, you can see it
says Samba version 4.1.17 found

00:08:10.270 --> 00:08:11.500 align:middle line:90%
with writable share.

00:08:11.500 --> 00:08:14.170 align:middle line:84%
In this case, we know that
the target is really not

00:08:14.170 --> 00:08:16.912 align:middle line:90%
running version 4.1.7.

00:08:16.912 --> 00:08:20.500 align:middle line:84%
However, we do know that this
particular exploit module runs

00:08:20.500 --> 00:08:24.730 align:middle line:90%
on version 3.5.0 to 4.4.14.

00:08:24.730 --> 00:08:27.050 align:middle line:84%
So it will work on
the target system.

00:08:27.050 --> 00:08:27.805 align:middle line:90%
So we can hit Run.

00:08:27.805 --> 00:08:32.390 align:middle line:90%


00:08:32.390 --> 00:08:34.820 align:middle line:84%
That is going to
execute the exploit

00:08:34.820 --> 00:08:37.440 align:middle line:84%
and is going to open up
a command shell session.

00:08:37.440 --> 00:08:39.559 align:middle line:90%
So again, we can type in LS.

00:08:39.559 --> 00:08:42.049 align:middle line:84%
And let's see whether
we get any output.

00:08:42.049 --> 00:08:45.650 align:middle line:84%
We can also try and run a
few other commands like PWD.

00:08:45.650 --> 00:08:48.260 align:middle line:84%
And as you can see, that will
print out our current working

00:08:48.260 --> 00:08:50.790 align:middle line:84%
directory on the
Linux target system.

00:08:50.790 --> 00:08:53.600 align:middle line:84%
So we can put this in the
background using the keyboard

00:08:53.600 --> 00:08:56.628 align:middle line:84%
combination Control and
Z. It's going to prompt

00:08:56.628 --> 00:08:57.920 align:middle line:90%
us to put it in the background.

00:08:57.920 --> 00:08:59.150 align:middle line:90%
I'm going to say Yes.

00:08:59.150 --> 00:09:02.270 align:middle line:84%
And if we type or list
out our sessions here,

00:09:02.270 --> 00:09:05.510 align:middle line:84%
you can see that we currently
have a command shell

00:09:05.510 --> 00:09:07.160 align:middle line:90%
session on the target.

00:09:07.160 --> 00:09:09.620 align:middle line:84%
We want to upgrade this
to a meterpreter session

00:09:09.620 --> 00:09:13.100 align:middle line:84%
because a meterpreter session
is much better in regards

00:09:13.100 --> 00:09:15.870 align:middle line:90%
to access on the target system.

00:09:15.870 --> 00:09:19.370 align:middle line:84%
So we are going to search for a
post-exploitation module called

00:09:19.370 --> 00:09:20.840 align:middle line:90%
shell to meterpreter.

00:09:20.840 --> 00:09:23.550 align:middle line:90%


00:09:23.550 --> 00:09:25.030 align:middle line:90%
And this is the module here.

00:09:25.030 --> 00:09:28.980 align:middle line:84%
So we're going to copy that and
say use, paste in the module

00:09:28.980 --> 00:09:29.550 align:middle line:90%
there.

00:09:29.550 --> 00:09:32.240 align:middle line:90%
We show the options.

00:09:32.240 --> 00:09:34.660 align:middle line:84%
In this case, we need to
set the Lhost option, that

00:09:34.660 --> 00:09:37.180 align:middle line:84%
is going to be the IP
address of the host that

00:09:37.180 --> 00:09:39.350 align:middle line:84%
will receive the connection
from the payload.

00:09:39.350 --> 00:09:42.670 align:middle line:84%
So this is going to be our
Kali Linux instance IP.

00:09:42.670 --> 00:09:45.160 align:middle line:84%
And then the Lport is going
to be the port for the payload

00:09:45.160 --> 00:09:46.210 align:middle line:90%
to connect to.

00:09:46.210 --> 00:09:49.240 align:middle line:84%
And then we need to set up the
session ID, which in this case

00:09:49.240 --> 00:09:51.970 align:middle line:84%
is 1 because that's the session
that we want to actually

00:09:51.970 --> 00:09:54.200 align:middle line:90%
upgrade or rather here it is.

00:09:54.200 --> 00:09:56.350 align:middle line:84%
So that's the actual
command session

00:09:56.350 --> 00:09:57.470 align:middle line:90%
that we want to upgrade.

00:09:57.470 --> 00:10:01.240 align:middle line:84%
So we'll set the Lhost value
to the IP address of the Kali

00:10:01.240 --> 00:10:02.840 align:middle line:90%
Linux instance.

00:10:02.840 --> 00:10:05.110 align:middle line:84%
And in this case, we can
utilize the interface name

00:10:05.110 --> 00:10:07.360 align:middle line:84%
to set the IP address
automatically,

00:10:07.360 --> 00:10:09.240 align:middle line:90%
and it does exactly that.

00:10:09.240 --> 00:10:10.990 align:middle line:84%
We're going to leave
the default port here

00:10:10.990 --> 00:10:13.000 align:middle line:84%
because that port
is currently open.

00:10:13.000 --> 00:10:17.560 align:middle line:84%
And we're then going to set
the session to 1 and hit Run.

00:10:17.560 --> 00:10:20.410 align:middle line:84%
And that's going to upgrade
our command shell session

00:10:20.410 --> 00:10:22.220 align:middle line:90%
into a meterpreter session.

00:10:22.220 --> 00:10:24.010 align:middle line:84%
So we're going to give
that a few seconds.

00:10:24.010 --> 00:10:24.552 align:middle line:90%
There we are.

00:10:24.552 --> 00:10:26.870 align:middle line:84%
It says meterpreter
session to open.

00:10:26.870 --> 00:10:28.960 align:middle line:84%
And if we list out
our sessions now,

00:10:28.960 --> 00:10:30.730 align:middle line:84%
you can see that we
have a meterpreter

00:10:30.730 --> 00:10:32.450 align:middle line:90%
session on the target system.

00:10:32.450 --> 00:10:35.760 align:middle line:84%
So if we type in
sessions 2, you can

00:10:35.760 --> 00:10:38.260 align:middle line:84%
see that we have a meterpreter
session on the target system.

00:10:38.260 --> 00:10:40.360 align:middle line:84%
And we can type in
the sysinfo command

00:10:40.360 --> 00:10:43.060 align:middle line:84%
to get an idea of what
the system is running

00:10:43.060 --> 00:10:46.420 align:middle line:84%
in regards to the distribution
release version as well

00:10:46.420 --> 00:10:47.620 align:middle line:90%
as the kernel version.

00:10:47.620 --> 00:10:50.770 align:middle line:84%
In this case, we can see the
target is running Debian 8.

00:10:50.770 --> 00:10:54.760 align:middle line:84%
And the Linux version or the
Linux kernel version is 5.4.

00:10:54.760 --> 00:10:57.070 align:middle line:84%
We can enumerate the
permissions that we currently

00:10:57.070 --> 00:10:59.350 align:middle line:90%
have by typing in get user ID.

00:10:59.350 --> 00:11:01.300 align:middle line:84%
And as you can see,
we have the user ID

00:11:01.300 --> 00:11:04.540 align:middle line:84%
of 0, which is the root user,
which consequently means

00:11:04.540 --> 00:11:06.220 align:middle line:84%
that we have the
highest privileges

00:11:06.220 --> 00:11:08.320 align:middle line:90%
available on the Linux target.

00:11:08.320 --> 00:11:10.480 align:middle line:84%
And consequently
means that we don't

00:11:10.480 --> 00:11:12.280 align:middle line:90%
need to elevate our privileges.

00:11:12.280 --> 00:11:15.820 align:middle line:84%
So that is how to
exploit Samba on Linux.

00:11:15.820 --> 00:11:18.820 align:middle line:84%
And that is going to conclude
the practical demonstration

00:11:18.820 --> 00:11:21.880 align:middle line:90%
within this video.

00:11:21.880 --> 00:11:24.510 align:middle line:84%
In the next video, we
are going to be exploring

00:11:24.510 --> 00:11:28.200 align:middle line:84%
the process of exploiting a
vulnerable SSH server running

00:11:28.200 --> 00:11:29.410 align:middle line:90%
on a Linux target.

00:11:29.410 --> 00:11:32.060 align:middle line:90%
So I'll see you there.

00:11:32.060 --> 00:11:33.000 align:middle line:90%