WEBVTT

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


00:00:10.210 --> 00:00:13.540 align:middle line:84%
Enumerating network
information on Linux.

00:00:13.540 --> 00:00:15.040 align:middle line:84%
In this video, we
will be exploring

00:00:15.040 --> 00:00:18.370 align:middle line:84%
the process of how to
enumerate various bits

00:00:18.370 --> 00:00:20.620 align:middle line:84%
or segments of
network information

00:00:20.620 --> 00:00:23.650 align:middle line:84%
that are really important
to, essentially,

00:00:23.650 --> 00:00:26.980 align:middle line:84%
obtain or gather during
post exploitation, right?

00:00:26.980 --> 00:00:28.660 align:middle line:84%
And we're going to
be focusing on how

00:00:28.660 --> 00:00:32.409 align:middle line:84%
to do this on a Linux system
that we will be compromising.

00:00:32.409 --> 00:00:35.200 align:middle line:84%
So again, you should have
a good idea as to why

00:00:35.200 --> 00:00:37.000 align:middle line:90%
this information is important.

00:00:37.000 --> 00:00:40.180 align:middle line:84%
And in regards to what
information we're looking for,

00:00:40.180 --> 00:00:42.740 align:middle line:84%
specific to Linux,
we are, of course,

00:00:42.740 --> 00:00:44.860 align:middle line:84%
going to need to
identify the current IP

00:00:44.860 --> 00:00:48.850 align:middle line:84%
address, which we pretty much
would have already obtained.

00:00:48.850 --> 00:00:51.550 align:middle line:84%
But we all also want to
obtain additional information

00:00:51.550 --> 00:00:54.820 align:middle line:84%
regarding the network adapter
or the network interface

00:00:54.820 --> 00:00:58.000 align:middle line:84%
card, and the gateway
address, as well

00:00:58.000 --> 00:01:02.710 align:middle line:84%
as additional information
like the actual hosts file

00:01:02.710 --> 00:01:06.550 align:middle line:84%
and the various hosts
contained within the hosts

00:01:06.550 --> 00:01:10.750 align:middle line:84%
file, the default DNS
server being used,

00:01:10.750 --> 00:01:14.290 align:middle line:84%
as well as internal networks
if this system is connected

00:01:14.290 --> 00:01:16.000 align:middle line:84%
or if the target
system is connected

00:01:16.000 --> 00:01:17.560 align:middle line:90%
to any internal networks.

00:01:17.560 --> 00:01:21.220 align:middle line:84%
We also want to get an idea
of the various TCP and UDP

00:01:21.220 --> 00:01:24.130 align:middle line:84%
services that are running
on the target system

00:01:24.130 --> 00:01:26.230 align:middle line:90%
and their respective ports.

00:01:26.230 --> 00:01:28.570 align:middle line:84%
And of course, try and
identify other hosts

00:01:28.570 --> 00:01:31.450 align:middle line:84%
on the network that we
can then pivot onto.

00:01:31.450 --> 00:01:34.600 align:middle line:84%
So again, network
information is really

00:01:34.600 --> 00:01:38.650 align:middle line:84%
important during the pivoting
phase of the post exploitation

00:01:38.650 --> 00:01:39.850 align:middle line:90%
phase.

00:01:39.850 --> 00:01:42.280 align:middle line:84%
So again, this is all
of the information

00:01:42.280 --> 00:01:44.500 align:middle line:84%
that we're going to be
looking for in regards

00:01:44.500 --> 00:01:47.420 align:middle line:84%
or in the context of
a Linux target system.

00:01:47.420 --> 00:01:49.990 align:middle line:84%
So we are going to be
utilizing the same lab

00:01:49.990 --> 00:01:52.070 align:middle line:84%
environment that we used
in the previous video.

00:01:52.070 --> 00:01:54.010 align:middle line:84%
So we're going to start
off by gaining access

00:01:54.010 --> 00:01:55.270 align:middle line:90%
to the target system.

00:01:55.270 --> 00:01:57.880 align:middle line:84%
We've already identified
the vulnerable service

00:01:57.880 --> 00:01:59.290 align:middle line:90%
that we'll be exploiting.

00:01:59.290 --> 00:02:02.440 align:middle line:84%
After which, we can begin
performing or enumerating

00:02:02.440 --> 00:02:03.730 align:middle line:90%
network information.

00:02:03.730 --> 00:02:06.130 align:middle line:84%
With that being said,
I'll be seeing you

00:02:06.130 --> 00:02:08.740 align:middle line:90%
in the actual lab environment.

00:02:08.740 --> 00:02:12.550 align:middle line:90%


00:02:12.550 --> 00:02:14.860 align:middle line:84%
All right, so I'm back
within the lab environment.

00:02:14.860 --> 00:02:17.890 align:middle line:84%
And of course, the first step
is to identify the target IP

00:02:17.890 --> 00:02:20.680 align:middle line:84%
address because it will change
whenever you restart the lab.

00:02:20.680 --> 00:02:23.920 align:middle line:84%
So we can type in ifconfig,
and we can take a look

00:02:23.920 --> 00:02:25.180 align:middle line:90%
at the interface ethernet1.

00:02:25.180 --> 00:02:27.190 align:middle line:90%
This is our Kali Linux IP.

00:02:27.190 --> 00:02:29.548 align:middle line:84%
In your case, this is
going to be different.

00:02:29.548 --> 00:02:31.090 align:middle line:84%
The only thing you
need to do is just

00:02:31.090 --> 00:02:34.330 align:middle line:84%
copy the value here and
change the 2 to a 3,

00:02:34.330 --> 00:02:36.200 align:middle line:84%
and that's the
target IP address.

00:02:36.200 --> 00:02:38.440 align:middle line:84%
So we already know
that the target

00:02:38.440 --> 00:02:42.940 align:middle line:84%
is running a vulnerable
version of vsftpd

00:02:42.940 --> 00:02:46.100 align:middle line:84%
that we can exploit using a
Metasploit framework exploit

00:02:46.100 --> 00:02:46.600 align:middle line:90%
module.

00:02:46.600 --> 00:02:50.020 align:middle line:84%
So I'll start off MSF
console, and that'll

00:02:50.020 --> 00:02:51.290 align:middle line:90%
take a couple of seconds.

00:02:51.290 --> 00:02:54.700 align:middle line:84%
After which, we can set
up the global variable

00:02:54.700 --> 00:02:57.100 align:middle line:90%
for the RHOSTS value or option.

00:02:57.100 --> 00:03:01.310 align:middle line:84%
So we can say, setg RHOSTS,
hosts and paste in the target

00:03:01.310 --> 00:03:01.810 align:middle line:90%
IP.

00:03:01.810 --> 00:03:05.680 align:middle line:84%
Make sure to change the 2 to
a 3, and we can hit Enter.

00:03:05.680 --> 00:03:10.310 align:middle line:84%
This is going to ensure that
RHOSTS value is set globally,

00:03:10.310 --> 00:03:13.240 align:middle line:84%
so that whenever we
load any module, really,

00:03:13.240 --> 00:03:15.950 align:middle line:84%
the RHOSTS value will
already be set for us.

00:03:15.950 --> 00:03:20.190 align:middle line:84%
So we can search for the
vsftpd exploit module.

00:03:20.190 --> 00:03:20.840 align:middle line:90%
There it is.

00:03:20.840 --> 00:03:23.530 align:middle line:84%
So I can then copy the
actual name of the exploit

00:03:23.530 --> 00:03:27.290 align:middle line:84%
module and say, use, and I
can then paste it in there.

00:03:27.290 --> 00:03:30.020 align:middle line:84%
And if I show the
options, you can

00:03:30.020 --> 00:03:32.300 align:middle line:84%
see that target IP
is already specified.

00:03:32.300 --> 00:03:34.910 align:middle line:84%
I can then type in
exploit, and we'll

00:03:34.910 --> 00:03:37.010 align:middle line:90%
give this a couple of seconds.

00:03:37.010 --> 00:03:37.602 align:middle line:90%
There we are.

00:03:37.602 --> 00:03:40.170 align:middle line:84%
We should obtain a
command shell session,

00:03:40.170 --> 00:03:42.740 align:middle line:84%
which we can then upgrade
to a Meterpreter session.

00:03:42.740 --> 00:03:45.380 align:middle line:84%
So I'll use the
control and Z keys

00:03:45.380 --> 00:03:48.120 align:middle line:84%
on my keyboard to put
this into the background.

00:03:48.120 --> 00:03:49.460 align:middle line:90%
So I'll say yes.

00:03:49.460 --> 00:03:51.170 align:middle line:84%
And if I'll start
my sessions, we

00:03:51.170 --> 00:03:54.470 align:middle line:84%
want to upgrade session 1, which
is our command shell session,

00:03:54.470 --> 00:03:55.970 align:middle line:90%
into a Meterpreter session.

00:03:55.970 --> 00:04:00.500 align:middle line:90%
So we can say, sessions -u1.

00:04:00.500 --> 00:04:01.280 align:middle line:90%
Hit Enter.

00:04:01.280 --> 00:04:03.650 align:middle line:84%
That is going to give
us a Meterpreter session

00:04:03.650 --> 00:04:07.100 align:middle line:84%
or upgrade our command shell
session into a Meterpreter

00:04:07.100 --> 00:04:07.760 align:middle line:90%
session.

00:04:07.760 --> 00:04:08.660 align:middle line:90%
There we are.

00:04:08.660 --> 00:04:11.090 align:middle line:84%
And if we list out
our sessions now,

00:04:11.090 --> 00:04:13.340 align:middle line:84%
we can now utilize
session 2, which

00:04:13.340 --> 00:04:14.670 align:middle line:90%
is our Meterpreter session.

00:04:14.670 --> 00:04:17.490 align:middle line:84%
So I'll say sessions
2, and there we are.

00:04:17.490 --> 00:04:20.630 align:middle line:84%
So let's take a look at how we
can perform network information

00:04:20.630 --> 00:04:22.910 align:middle line:84%
enumeration with my
interpreter first.

00:04:22.910 --> 00:04:25.310 align:middle line:84%
So again, like we
did on Windows,

00:04:25.310 --> 00:04:29.990 align:middle line:84%
you can obtain the current IP
address and the actual network

00:04:29.990 --> 00:04:33.740 align:middle line:84%
interface details by
typing in ifconfig.

00:04:33.740 --> 00:04:35.930 align:middle line:84%
And you can see right
over here that we

00:04:35.930 --> 00:04:37.760 align:middle line:90%
have various interfaces.

00:04:37.760 --> 00:04:39.860 align:middle line:84%
So we have the first
interface, which

00:04:39.860 --> 00:04:41.750 align:middle line:90%
is your loopback interface.

00:04:41.750 --> 00:04:43.070 align:middle line:90%
This is standard on Linux.

00:04:43.070 --> 00:04:46.850 align:middle line:84%
That is your local host
or your loopback adapter.

00:04:46.850 --> 00:04:51.350 align:middle line:84%
That is essentially configured
for your local services

00:04:51.350 --> 00:04:54.020 align:middle line:84%
or essentially configured
to your local host IP

00:04:54.020 --> 00:04:57.740 align:middle line:90%
address, which is 127.0.0.1.

00:04:57.740 --> 00:05:02.240 align:middle line:84%
We then have interface 2,
which is highlighted here.

00:05:02.240 --> 00:05:04.700 align:middle line:84%
Interface 2, in
this case, appears

00:05:04.700 --> 00:05:08.000 align:middle line:84%
to be a virtual interface,
which, in this case,

00:05:08.000 --> 00:05:09.540 align:middle line:90%
is not really important.

00:05:09.540 --> 00:05:12.500 align:middle line:84%
But then, we have
Interface 6180, which

00:05:12.500 --> 00:05:14.450 align:middle line:90%
has the name of ethernet 0.

00:05:14.450 --> 00:05:16.340 align:middle line:84%
Remember, this is on
the target system.

00:05:16.340 --> 00:05:18.720 align:middle line:84%
This is not on the
Kali Linux system.

00:05:18.720 --> 00:05:22.040 align:middle line:84%
It provides us with the
MAC address right over here

00:05:22.040 --> 00:05:24.080 align:middle line:90%
of this particular interface.

00:05:24.080 --> 00:05:26.730 align:middle line:84%
It then provides us
with the IPv4 address.

00:05:26.730 --> 00:05:30.410 align:middle line:84%
So this is the target IP
address as we already know.

00:05:30.410 --> 00:05:35.000 align:middle line:84%
We can also obtain or get a
list of the currently running

00:05:35.000 --> 00:05:39.630 align:middle line:84%
TCP and UDP services by
typing in the netstat command.

00:05:39.630 --> 00:05:41.720 align:middle line:84%
So we hit Enter, and
you can see this will

00:05:41.720 --> 00:05:43.440 align:middle line:90%
display the connection list.

00:05:43.440 --> 00:05:46.940 align:middle line:84%
So this is sorted based on
protocol-- the Local Address,

00:05:46.940 --> 00:05:50.480 align:middle line:84%
the Remote Address, the
State, the User, the Inode,

00:05:50.480 --> 00:05:55.110 align:middle line:84%
and the PID, which is the
process ID or the program name.

00:05:55.110 --> 00:05:57.530 align:middle line:84%
So firstly, you have
your TCP connections.

00:05:57.530 --> 00:06:00.140 align:middle line:84%
And then, at the bottom, you
have your UDP connection.

00:06:00.140 --> 00:06:05.060 align:middle line:84%
So you can see that port 21 is
listening on the local address

00:06:05.060 --> 00:06:05.810 align:middle line:90%
on--

00:06:05.810 --> 00:06:09.680 align:middle line:84%
this is the actual
vsftpd service

00:06:09.680 --> 00:06:11.480 align:middle line:90%
that is running on port 21.

00:06:11.480 --> 00:06:14.630 align:middle line:84%
You can see the state
is set to listen,

00:06:14.630 --> 00:06:17.210 align:middle line:90%
and the remote address is 0.

00:06:17.210 --> 00:06:20.270 align:middle line:84%
You then have a port 6200,
which is interesting.

00:06:20.270 --> 00:06:22.910 align:middle line:84%
That gives us an idea as to
what other services might

00:06:22.910 --> 00:06:25.850 align:middle line:90%
be running on specific ports.

00:06:25.850 --> 00:06:28.050 align:middle line:90%
You then have the following.

00:06:28.050 --> 00:06:32.000 align:middle line:84%
It looks like we have-- this
is listing on the local host

00:06:32.000 --> 00:06:33.440 align:middle line:90%
with--

00:06:33.440 --> 00:06:35.030 align:middle line:84%
not really the local
host because it

00:06:35.030 --> 00:06:42.530 align:middle line:84%
is 127.0.0.11 on port
38275, but it's currently--

00:06:42.530 --> 00:06:44.720 align:middle line:90%
the state is said to listen.

00:06:44.720 --> 00:06:47.720 align:middle line:84%
What we're interested
in is the established,

00:06:47.720 --> 00:06:50.330 align:middle line:84%
in this case, because we
are trying to identify

00:06:50.330 --> 00:06:51.980 align:middle line:90%
our Meterpreter session.

00:06:51.980 --> 00:06:56.060 align:middle line:84%
So given the fact that our
Meterpreter session utilized

00:06:56.060 --> 00:07:01.250 align:middle line:84%
or set up the actual L
port value was set 4433.

00:07:01.250 --> 00:07:03.230 align:middle line:90%
This is our Meterpreter session.

00:07:03.230 --> 00:07:05.780 align:middle line:84%
You can see this is the
Kali Linux IP address,

00:07:05.780 --> 00:07:09.020 align:middle line:84%
and we are connecting-- or
rather, the target system is

00:07:09.020 --> 00:07:12.470 align:middle line:84%
connecting to our
listener on port 4433,

00:07:12.470 --> 00:07:14.060 align:middle line:90%
and it is set to establish.

00:07:14.060 --> 00:07:17.840 align:middle line:84%
So again, this gives you
an idea of what TCP and UDP

00:07:17.840 --> 00:07:21.590 align:middle line:84%
services are currently listening
or running on the target

00:07:21.590 --> 00:07:24.320 align:middle line:84%
system, as well as
providing you with an idea

00:07:24.320 --> 00:07:27.230 align:middle line:90%
of various connections.

00:07:27.230 --> 00:07:30.710 align:middle line:84%
And it sorts them based on their
state, so you can go through it

00:07:30.710 --> 00:07:34.730 align:middle line:84%
and identify state or services
that are currently listening

00:07:34.730 --> 00:07:39.010 align:middle line:84%
or services that currently
have a connection established,

00:07:39.010 --> 00:07:40.560 align:middle line:90%
et cetera, et cetera.

00:07:40.560 --> 00:07:43.250 align:middle line:84%
You can also display the
routing table with Meterpreter

00:07:43.250 --> 00:07:45.290 align:middle line:90%
by simply typing in route.

00:07:45.290 --> 00:07:48.500 align:middle line:84%
And in this case, it'll
display the routing table.

00:07:48.500 --> 00:07:51.440 align:middle line:84%
So the key information that
we're interested in here

00:07:51.440 --> 00:07:52.730 align:middle line:90%
is the gateway, right?

00:07:52.730 --> 00:07:57.230 align:middle line:84%
So it looks like the gateway
on this target network

00:07:57.230 --> 00:07:58.920 align:middle line:90%
is the following address here.

00:07:58.920 --> 00:08:03.140 align:middle line:84%
So it's going to be the first
IP address within this network.

00:08:03.140 --> 00:08:06.350 align:middle line:84%
And yeah, that's very
important information.

00:08:06.350 --> 00:08:09.320 align:middle line:84%
Because in some networks,
this may be the router

00:08:09.320 --> 00:08:13.490 align:middle line:84%
or it could also be the DNS
server and the DHCP server

00:08:13.490 --> 00:08:14.600 align:middle line:90%
all in one, right?

00:08:14.600 --> 00:08:17.030 align:middle line:90%
So that's very, very important.

00:08:17.030 --> 00:08:20.450 align:middle line:84%
It also tells us that no
IPv6 routes were found.

00:08:20.450 --> 00:08:23.420 align:middle line:84%
Now, that we've taken a look
at how to essentially enumerate

00:08:23.420 --> 00:08:25.610 align:middle line:84%
network information
with Meterpreter,

00:08:25.610 --> 00:08:28.100 align:middle line:84%
we can open up a
command shell session.

00:08:28.100 --> 00:08:30.510 align:middle line:84%
And I'll open up a
bash session here.

00:08:30.510 --> 00:08:32.659 align:middle line:90%
So /bin/bash -i.

00:08:32.659 --> 00:08:33.169 align:middle line:90%
There we go.

00:08:33.169 --> 00:08:33.950 align:middle line:90%
Fantastic.

00:08:33.950 --> 00:08:37.730 align:middle line:84%
And we can run the
ifconfig command,

00:08:37.730 --> 00:08:38.900 align:middle line:90%
which is a Linux command.

00:08:38.900 --> 00:08:42.169 align:middle line:84%
And that'll essentially--
in some cases,

00:08:42.169 --> 00:08:44.630 align:middle line:84%
it'll tell you that the
command is not found.

00:08:44.630 --> 00:08:46.520 align:middle line:84%
That just comes down
to the distribution

00:08:46.520 --> 00:08:48.740 align:middle line:84%
that you have just
gained access to.

00:08:48.740 --> 00:08:51.600 align:middle line:84%
A quick way around this
is to use the IP command.

00:08:51.600 --> 00:08:54.470 align:middle line:84%
So I can say ip
a and s, and this

00:08:54.470 --> 00:08:58.400 align:middle line:84%
will display all the interfaces
or the actual adaptors.

00:08:58.400 --> 00:09:02.060 align:middle line:84%
So as we were able to
obtain it with Meterpreter,

00:09:02.060 --> 00:09:04.970 align:middle line:84%
you can see that we have
interface 1, 2, and then,

00:09:04.970 --> 00:09:08.810 align:middle line:84%
of course, the third
interface, which is ethernet 0.

00:09:08.810 --> 00:09:12.260 align:middle line:84%
And this, of course, contains
the inet or the IP address

00:09:12.260 --> 00:09:16.280 align:middle line:84%
of the target system as well
as additional information

00:09:16.280 --> 00:09:19.520 align:middle line:84%
like the MAC address
right over here.

00:09:19.520 --> 00:09:21.900 align:middle line:84%
All right, so you
can utilize ifconfig

00:09:21.900 --> 00:09:24.920 align:middle line:90%
or the ip a s command, right?

00:09:24.920 --> 00:09:28.280 align:middle line:84%
And that'll give you an idea
as to all the interfaces

00:09:28.280 --> 00:09:31.320 align:middle line:84%
that are essentially connected
to the target system,

00:09:31.320 --> 00:09:34.640 align:middle line:84%
and this is where you
typically find other networks

00:09:34.640 --> 00:09:37.570 align:middle line:90%
that you can pivot to.

00:09:37.570 --> 00:09:42.170 align:middle line:84%
We can also, again, get all the
contents of the networks file.

00:09:42.170 --> 00:09:45.010 align:middle line:90%
So I can say, cat/etc/networks.

00:09:45.010 --> 00:09:45.850 align:middle line:90%
There we are.

00:09:45.850 --> 00:09:49.990 align:middle line:84%
And this will essentially
display a list of interfaces

00:09:49.990 --> 00:09:51.470 align:middle line:90%
and the configuration.

00:09:51.470 --> 00:09:55.390 align:middle line:84%
So you can see that we have
the default interface loopback

00:09:55.390 --> 00:09:57.550 align:middle line:90%
and the link-local, right?

00:09:57.550 --> 00:10:02.090 align:middle line:84%
So whenever-- if the ifconfig
utility is not installed,

00:10:02.090 --> 00:10:04.870 align:middle line:84%
then you can utilize
the ip a s command

00:10:04.870 --> 00:10:10.060 align:middle line:84%
or you cut all the content
of the etc/networks file.

00:10:10.060 --> 00:10:11.830 align:middle line:84%
We can, of course, get
the hostname, which

00:10:11.830 --> 00:10:13.810 align:middle line:84%
we have obtained
previously, and that

00:10:13.810 --> 00:10:16.210 align:middle line:84%
can be done by cutting
out the content

00:10:16.210 --> 00:10:20.528 align:middle line:90%
of the etc/hostname file.

00:10:20.528 --> 00:10:21.070 align:middle line:90%
There we are.

00:10:21.070 --> 00:10:23.500 align:middle line:84%
And you can see, we already
know that the system--

00:10:23.500 --> 00:10:26.010 align:middle line:90%
the host name is victim1.

00:10:26.010 --> 00:10:30.480 align:middle line:84%
If we want to essentially
enumerate the content

00:10:30.480 --> 00:10:35.190 align:middle line:84%
of the hosts file, we can do
that by saying cat /etc/hosts,

00:10:35.190 --> 00:10:37.980 align:middle line:84%
and this will essentially-- this
will essentially show you all

00:10:37.980 --> 00:10:43.410 align:middle line:84%
the hosts as well as the
actual domain pertinent to that

00:10:43.410 --> 00:10:44.690 align:middle line:90%
particular IP address.

00:10:44.690 --> 00:10:47.140 align:middle line:84%
So again, this can
be quite important

00:10:47.140 --> 00:10:50.370 align:middle line:84%
if you are trying to identify
internal domains that you

00:10:50.370 --> 00:10:51.970 align:middle line:90%
can access.

00:10:51.970 --> 00:10:54.690 align:middle line:84%
So again, this is
configured locally.

00:10:54.690 --> 00:10:59.460 align:middle line:84%
So again, for example,
if I added another host,

00:10:59.460 --> 00:11:01.650 align:middle line:84%
I could add the
Kali Linux system

00:11:01.650 --> 00:11:04.380 align:middle line:84%
and specify the IP address
of the Kali Linux system.

00:11:04.380 --> 00:11:06.990 align:middle line:84%
And again, that is
something that we'll

00:11:06.990 --> 00:11:10.290 align:middle line:84%
be exploring during
the actual pivoting

00:11:10.290 --> 00:11:12.460 align:middle line:90%
section of this course.

00:11:12.460 --> 00:11:16.320 align:middle line:84%
We can also display the
DNS information by cutting

00:11:16.320 --> 00:11:21.010 align:middle line:84%
the contents of the
/etc/resolv.conf file.

00:11:21.010 --> 00:11:23.670 align:middle line:90%
So resolv.conf.

00:11:23.670 --> 00:11:26.400 align:middle line:84%
If I hit Enter, this will
display the main name server.

00:11:26.400 --> 00:11:30.370 align:middle line:84%
This is the DNS server that is
used by default. In this case,

00:11:30.370 --> 00:11:33.870 align:middle line:90%
it connects to 127.0.0.11.

00:11:33.870 --> 00:11:36.540 align:middle line:84%
If you're working
within a real network,

00:11:36.540 --> 00:11:40.560 align:middle line:84%
then this will typically
be the default gateway.

00:11:40.560 --> 00:11:44.200 align:middle line:84%
Not in all cases, but
in the case of Linux.

00:11:44.200 --> 00:11:46.290 align:middle line:84%
But in this case, because
this target system

00:11:46.290 --> 00:11:50.010 align:middle line:84%
is running on Leonard, which
is a cloud-hosting provider,

00:11:50.010 --> 00:11:53.160 align:middle line:84%
it is going to utilize the
default name server specified

00:11:53.160 --> 00:11:55.080 align:middle line:90%
by Leonard, right?

00:11:55.080 --> 00:11:58.320 align:middle line:84%
So yeah, that's how to
display the DNS information

00:11:58.320 --> 00:12:00.760 align:middle line:84%
or configuration
for that matter.

00:12:00.760 --> 00:12:03.930 align:middle line:84%
Now, if you want to
find other systems

00:12:03.930 --> 00:12:08.970 align:middle line:84%
or you want to display the ARP
table, which, essentially, will

00:12:08.970 --> 00:12:10.830 align:middle line:84%
give you an idea
of other systems

00:12:10.830 --> 00:12:14.730 align:middle line:84%
that are part of the network
that the target system you have

00:12:14.730 --> 00:12:18.330 align:middle line:84%
compromised is a part of, you
can, again, run the ARP command

00:12:18.330 --> 00:12:19.830 align:middle line:90%
and say, arp -a.

00:12:19.830 --> 00:12:22.050 align:middle line:84%
And if the command
is not installed,

00:12:22.050 --> 00:12:23.310 align:middle line:90%
that's perfectly fine.

00:12:23.310 --> 00:12:25.740 align:middle line:84%
If the ARP utility is
not stored, as I said,

00:12:25.740 --> 00:12:27.520 align:middle line:90%
that's perfectly fine.

00:12:27.520 --> 00:12:30.900 align:middle line:84%
What we can do is we can
terminate this command shell

00:12:30.900 --> 00:12:34.440 align:middle line:84%
session, and we can go back into
our Meterpreter session, which

00:12:34.440 --> 00:12:35.460 align:middle line:90%
looks like it's died.

00:12:35.460 --> 00:12:37.770 align:middle line:84%
So if we list all
sessions, I'm just

00:12:37.770 --> 00:12:40.800 align:middle line:84%
going to upgrade
session 1 once more

00:12:40.800 --> 00:12:42.570 align:middle line:84%
to show you how to
work around that

00:12:42.570 --> 00:12:46.140 align:middle line:84%
and how to actually get
information regarding

00:12:46.140 --> 00:12:49.330 align:middle line:84%
other systems that are
connected to the network.

00:12:49.330 --> 00:12:51.240 align:middle line:84%
So I'll say,
sessions once again.

00:12:51.240 --> 00:12:54.570 align:middle line:84%
And the Meterpreter session
is now in session 3.

00:12:54.570 --> 00:12:57.510 align:middle line:84%
So if I open up the Help
menu for Meterpreter,

00:12:57.510 --> 00:13:00.720 align:middle line:84%
you can see right over here
on the Networking Commands,

00:13:00.720 --> 00:13:05.080 align:middle line:84%
we can utilize the ARP command
to display the host ARP cache.

00:13:05.080 --> 00:13:06.810 align:middle line:90%
So I can say, arp.

00:13:06.810 --> 00:13:08.460 align:middle line:84%
And in this case,
you can see that we

00:13:08.460 --> 00:13:11.340 align:middle line:84%
don't have any other
systems connected

00:13:11.340 --> 00:13:14.550 align:middle line:84%
to this particular
network subnet, right?

00:13:14.550 --> 00:13:17.820 align:middle line:84%
So again, if we were performing
pivoting or we would like to--

00:13:17.820 --> 00:13:21.360 align:middle line:84%
if we wanted to identify
systems that we can pivot to,

00:13:21.360 --> 00:13:24.840 align:middle line:84%
then we would typically utilize
this command in conjunction

00:13:24.840 --> 00:13:26.640 align:middle line:90%
with a few others.

00:13:26.640 --> 00:13:30.060 align:middle line:84%
All right, so that is how to
perform network information

00:13:30.060 --> 00:13:31.587 align:middle line:90%
enumeration on Linux.

00:13:31.587 --> 00:13:33.420 align:middle line:84%
We have gathered quite
a lot of information.

00:13:33.420 --> 00:13:36.660 align:middle line:84%
As I said, when working
in a real environment,

00:13:36.660 --> 00:13:38.490 align:middle line:84%
all of the information
you will be getting

00:13:38.490 --> 00:13:40.830 align:middle line:90%
is equally as important.

00:13:40.830 --> 00:13:45.120 align:middle line:84%
And of course, in this case,
because this is a very simple

00:13:45.120 --> 00:13:48.690 align:middle line:84%
system, we haven't
been able to identify

00:13:48.690 --> 00:13:51.180 align:middle line:84%
any other internal
networks, but we

00:13:51.180 --> 00:13:53.310 align:middle line:84%
will be covering this
during the pivoting

00:13:53.310 --> 00:13:54.700 align:middle line:90%
section of this course.

00:13:54.700 --> 00:13:56.460 align:middle line:84%
With that being
said, that is going

00:13:56.460 --> 00:13:58.350 align:middle line:84%
to conclude the
practical demonstration

00:13:58.350 --> 00:14:00.780 align:middle line:90%
side of this video.

00:14:00.780 --> 00:14:02.600 align:middle line:84%
In the next video,
we will be exploring

00:14:02.600 --> 00:14:05.270 align:middle line:84%
the process of how to
enumerate services and cron

00:14:05.270 --> 00:14:07.620 align:middle line:90%
jobs on a Linux target system.

00:14:07.620 --> 00:14:11.500 align:middle line:84%
So I'll be seeing you
in the next video.

00:14:11.500 --> 00:14:12.000 align:middle line:90%