WEBVTT

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


00:00:04.810 --> 00:00:08.658 align:middle line:90%
[MUSIC PLAYING]

00:00:08.658 --> 00:00:10.110 align:middle line:90%


00:00:10.110 --> 00:00:14.220 align:middle line:84%
Windows Local Enumeration--
welcome to the second section

00:00:14.220 --> 00:00:17.610 align:middle line:84%
of this course where we
will be taking a look at how

00:00:17.610 --> 00:00:19.530 align:middle line:90%
to perform local enumeration.

00:00:19.530 --> 00:00:21.600 align:middle line:84%
More specifically,
we'll be exploring

00:00:21.600 --> 00:00:24.925 align:middle line:84%
how to perform local
enumeration on a Windows target.

00:00:24.925 --> 00:00:26.550 align:middle line:84%
In this video, we're
going to start off

00:00:26.550 --> 00:00:29.970 align:middle line:84%
by taking a look at how to
enumerate system information.

00:00:29.970 --> 00:00:33.820 align:middle line:84%
So let's get an understanding
of why this is so important.

00:00:33.820 --> 00:00:37.260 align:middle line:84%
So after gaining initial
access to a target system,

00:00:37.260 --> 00:00:39.150 align:middle line:84%
it is always important
to learn more

00:00:39.150 --> 00:00:42.460 align:middle line:84%
about the system, like what
operating system is running,

00:00:42.460 --> 00:00:44.760 align:middle line:84%
as well as the operating
system version.

00:00:44.760 --> 00:00:46.860 align:middle line:84%
This information is
very, very useful

00:00:46.860 --> 00:00:49.170 align:middle line:84%
as it gives us an
idea of what we can do

00:00:49.170 --> 00:00:51.580 align:middle line:84%
and what type of
exploits we can run.

00:00:51.580 --> 00:00:55.320 align:middle line:84%
So in the context of Windows
systems, what information

00:00:55.320 --> 00:00:58.600 align:middle line:84%
are we looking for specifically
regarding the system?

00:00:58.600 --> 00:01:00.510 align:middle line:84%
Firstly, we're looking
for the hostname.

00:01:00.510 --> 00:01:05.129 align:middle line:84%
So that will give us an idea
as to what purpose or function

00:01:05.129 --> 00:01:09.220 align:middle line:84%
this target system performs
within a company's network.

00:01:09.220 --> 00:01:12.660 align:middle line:84%
So for example, if the host
name of the system is Bob,

00:01:12.660 --> 00:01:15.450 align:middle line:84%
then we pretty much
know that system will

00:01:15.450 --> 00:01:17.160 align:middle line:90%
belong to a user called Bob.

00:01:17.160 --> 00:01:21.000 align:middle line:84%
If the host name is set to
Windows Server, et cetera,

00:01:21.000 --> 00:01:23.700 align:middle line:84%
then we know that
it's a Windows Server.

00:01:23.700 --> 00:01:25.560 align:middle line:84%
What other information
are we looking for?

00:01:25.560 --> 00:01:27.910 align:middle line:84%
The operating system
name or version--

00:01:27.910 --> 00:01:29.310 align:middle line:84%
so in the case of
Windows, we are

00:01:29.310 --> 00:01:32.580 align:middle line:84%
trying to identify the exact
version of the operating system

00:01:32.580 --> 00:01:33.790 align:middle line:90%
that's running on the target.

00:01:33.790 --> 00:01:36.248 align:middle line:84%
So we're trying to identify
whether it's Windows 7, Windows

00:01:36.248 --> 00:01:40.380 align:middle line:84%
8, Windows XP, Windows Server
2012, Windows 10, et cetera, et

00:01:40.380 --> 00:01:41.410 align:middle line:90%
cetera.

00:01:41.410 --> 00:01:43.200 align:middle line:84%
We also want to
identify the operating

00:01:43.200 --> 00:01:44.940 align:middle line:90%
system build and service pack.

00:01:44.940 --> 00:01:49.170 align:middle line:84%
So once we have identified
the operating system

00:01:49.170 --> 00:01:52.660 align:middle line:84%
version or the actual
release or addition,

00:01:52.660 --> 00:01:55.830 align:middle line:84%
we also need to identify
what service pack is running

00:01:55.830 --> 00:01:59.320 align:middle line:84%
and what build number
is actually running.

00:01:59.320 --> 00:02:01.980 align:middle line:84%
So an example of
this would be Windows

00:02:01.980 --> 00:02:05.250 align:middle line:90%
7 service pack 1 build 7600.

00:02:05.250 --> 00:02:08.020 align:middle line:84%
Now, you might be asking
yourself the question,

00:02:08.020 --> 00:02:11.250 align:middle line:84%
why is this
information important

00:02:11.250 --> 00:02:13.860 align:middle line:84%
whenever you perform your
pen test, more specifically,

00:02:13.860 --> 00:02:17.010 align:middle line:84%
during post exploitation
Well, this information

00:02:17.010 --> 00:02:20.220 align:middle line:84%
is extremely useful during
the privilege escalation

00:02:20.220 --> 00:02:24.060 align:middle line:84%
phase of post-exploitation
because whenever it comes down

00:02:24.060 --> 00:02:27.570 align:middle line:84%
to privilege
escalation on Windows,

00:02:27.570 --> 00:02:30.870 align:middle line:84%
the vulnerabilities that can be
exploited in order to elevate

00:02:30.870 --> 00:02:35.640 align:middle line:84%
your privileges will
really come down

00:02:35.640 --> 00:02:38.310 align:middle line:84%
to what specific
version of Windows

00:02:38.310 --> 00:02:41.250 align:middle line:84%
is running on the target in
addition to the service pack

00:02:41.250 --> 00:02:42.138 align:middle line:90%
and build number.

00:02:42.138 --> 00:02:43.680 align:middle line:84%
And this is something
that we've been

00:02:43.680 --> 00:02:47.880 align:middle line:84%
able to explore and elaborate
on in previous courses

00:02:47.880 --> 00:02:50.340 align:middle line:84%
like the Metasploit
framework course, system

00:02:50.340 --> 00:02:52.530 align:middle line:84%
and host-based
attacks, et cetera.

00:02:52.530 --> 00:02:56.490 align:middle line:84%
So this information gives us
an idea of what is running

00:02:56.490 --> 00:03:00.000 align:middle line:84%
on the target and what
we can and cannot do.

00:03:00.000 --> 00:03:03.360 align:middle line:84%
Another example of this
would be if we gain access

00:03:03.360 --> 00:03:05.460 align:middle line:90%
to a Windows XP system.

00:03:05.460 --> 00:03:08.940 align:middle line:84%
And in order to elevate our
privileges, for example,

00:03:08.940 --> 00:03:11.370 align:middle line:84%
we need to get the
exact service pack

00:03:11.370 --> 00:03:12.930 align:middle line:84%
version of the
service pack that's

00:03:12.930 --> 00:03:15.850 align:middle line:90%
running on the target system.

00:03:15.850 --> 00:03:17.880 align:middle line:84%
Another important
piece of information

00:03:17.880 --> 00:03:20.400 align:middle line:84%
is the operating
system architecture.

00:03:20.400 --> 00:03:24.390 align:middle line:84%
So what architecture of Windows
is running on the target?

00:03:24.390 --> 00:03:26.610 align:middle line:84%
Is it a 64-bit
version of Windows?

00:03:26.610 --> 00:03:28.830 align:middle line:84%
Is it a 32-bit
version of Windows?

00:03:28.830 --> 00:03:30.430 align:middle line:90%
Why is this important?

00:03:30.430 --> 00:03:32.130 align:middle line:90%
Well, let's use another example.

00:03:32.130 --> 00:03:34.230 align:middle line:84%
Let's say I'm
compiling an exploit

00:03:34.230 --> 00:03:36.960 align:middle line:84%
that I want to transfer over
to the target system that

00:03:36.960 --> 00:03:39.750 align:middle line:84%
will elevate our
privileges, for example.

00:03:39.750 --> 00:03:42.900 align:middle line:84%
Well, the actual
compilation process

00:03:42.900 --> 00:03:46.260 align:middle line:84%
will depend on the target
system's architecture

00:03:46.260 --> 00:03:48.720 align:middle line:84%
or the target operating
system's architecture.

00:03:48.720 --> 00:03:52.470 align:middle line:84%
So if the system is running
a 32-bit version of Windows,

00:03:52.470 --> 00:03:54.300 align:middle line:84%
that means that
I need to compile

00:03:54.300 --> 00:03:57.180 align:middle line:90%
a 32-bit exploit or executable.

00:03:57.180 --> 00:03:58.920 align:middle line:84%
And another example
of this would

00:03:58.920 --> 00:04:02.010 align:middle line:84%
be if I'm generating
a meterpreter payload

00:04:02.010 --> 00:04:03.720 align:middle line:90%
with msfvenom.

00:04:03.720 --> 00:04:06.510 align:middle line:84%
If the target is running a
32-bit version of Windows,

00:04:06.510 --> 00:04:09.540 align:middle line:84%
I need to generate a
32-bit meterpreter payload.

00:04:09.540 --> 00:04:11.910 align:middle line:84%
If it's running a 64-bit
version of Windows,

00:04:11.910 --> 00:04:13.450 align:middle line:90%
I need to adjust accordingly.

00:04:13.450 --> 00:04:15.720 align:middle line:84%
So if you don't get
that information,

00:04:15.720 --> 00:04:19.110 align:middle line:84%
then you really don't know what
type of payloads or executables

00:04:19.110 --> 00:04:21.690 align:middle line:84%
you need to generate
or the executables

00:04:21.690 --> 00:04:24.330 align:middle line:84%
that can be executed
on the target system

00:04:24.330 --> 00:04:25.960 align:middle line:90%
without any issues.

00:04:25.960 --> 00:04:29.280 align:middle line:84%
And lastly, we also want to
identify the installed updates

00:04:29.280 --> 00:04:30.420 align:middle line:90%
and HotFixes.

00:04:30.420 --> 00:04:33.330 align:middle line:84%
And this will tie into
the privilege escalation

00:04:33.330 --> 00:04:35.940 align:middle line:84%
phase of post-exploitation
primarily

00:04:35.940 --> 00:04:40.920 align:middle line:84%
because if you gain
access to a Windows system

00:04:40.920 --> 00:04:43.470 align:middle line:84%
and you want to
elevate your privileges

00:04:43.470 --> 00:04:46.260 align:middle line:84%
and you utilize the information
that you've gathered

00:04:46.260 --> 00:04:48.360 align:middle line:84%
like the operating
system edition

00:04:48.360 --> 00:04:50.520 align:middle line:84%
so you know that it's
running Windows 7,

00:04:50.520 --> 00:04:54.150 align:middle line:84%
you know that it's running
Windows 7 service pack 1 7600,

00:04:54.150 --> 00:04:57.960 align:middle line:84%
and you identify your privilege
escalation exploit online

00:04:57.960 --> 00:05:00.180 align:middle line:84%
and you want to use
it in order to elevate

00:05:00.180 --> 00:05:03.430 align:middle line:84%
your privileges, well, that
might not necessarily work.

00:05:03.430 --> 00:05:06.820 align:middle line:84%
And this is where the process
of enumerating installed updates

00:05:06.820 --> 00:05:08.770 align:middle line:84%
or HotFixes comes
into play because

00:05:08.770 --> 00:05:11.470 align:middle line:84%
that specific vulnerability
might have been patched.

00:05:11.470 --> 00:05:15.310 align:middle line:84%
And how do you know
whether it's been patched?

00:05:15.310 --> 00:05:18.490 align:middle line:84%
You identify that by enumerating
the installed updates

00:05:18.490 --> 00:05:19.600 align:middle line:90%
or HotFixes.

00:05:19.600 --> 00:05:22.900 align:middle line:84%
So enumerating this
information will tell you

00:05:22.900 --> 00:05:25.450 align:middle line:84%
what exploits you can run
and what vulnerabilities

00:05:25.450 --> 00:05:26.380 align:middle line:90%
have been patched.

00:05:26.380 --> 00:05:29.500 align:middle line:84%
So again, this is very,
very important information.

00:05:29.500 --> 00:05:31.540 align:middle line:84%
And again, to
demonstrate this, I'm

00:05:31.540 --> 00:05:33.290 align:middle line:84%
going to be using
a lab environment.

00:05:33.290 --> 00:05:38.420 align:middle line:84%
So this video has a lab
environment attached to it.

00:05:38.420 --> 00:05:40.280 align:middle line:84%
So all you need to do
is just fire it up,

00:05:40.280 --> 00:05:41.900 align:middle line:90%
and again, we can begin.

00:05:41.900 --> 00:05:45.550 align:middle line:84%
So we are going to be exploiting
the target system first.

00:05:45.550 --> 00:05:47.050 align:middle line:84%
So we're going to
be gaining access,

00:05:47.050 --> 00:05:50.200 align:middle line:84%
and then we can perform
the system enumeration.

00:05:50.200 --> 00:05:53.260 align:middle line:84%
So I'll see you within
the lab environment.

00:05:53.260 --> 00:05:57.410 align:middle line:90%


00:05:57.410 --> 00:05:59.990 align:middle line:84%
All right, so I'm back
within the lab environment.

00:05:59.990 --> 00:06:02.870 align:middle line:84%
And as you can see, you will
be provided with the target

00:06:02.870 --> 00:06:04.610 align:middle line:90%
system's IP address.

00:06:04.610 --> 00:06:06.260 align:middle line:84%
And in your case,
it'll be different.

00:06:06.260 --> 00:06:08.570 align:middle line:84%
All you need to do
is just copy that IP,

00:06:08.570 --> 00:06:11.930 align:middle line:84%
and we can get started with the
first step, which is gaining

00:06:11.930 --> 00:06:13.740 align:middle line:90%
access to the target system.

00:06:13.740 --> 00:06:16.100 align:middle line:84%
So in order to exploit
it, we're going

00:06:16.100 --> 00:06:18.260 align:middle line:84%
to firstly need to
perform a port scan

00:06:18.260 --> 00:06:21.240 align:middle line:84%
to identify the vulnerable
service that's running on it.

00:06:21.240 --> 00:06:22.890 align:middle line:90%
So I've opened up a terminal.

00:06:22.890 --> 00:06:25.960 align:middle line:84%
So we'll start off by performing
an Nmap scan on the target

00:06:25.960 --> 00:06:26.460 align:middle line:90%
service.

00:06:26.460 --> 00:06:30.380 align:middle line:84%
So we can perform a quick
service version detection scan,

00:06:30.380 --> 00:06:33.320 align:middle line:84%
and we'll just scan the
default, or we'll utilize

00:06:33.320 --> 00:06:35.750 align:middle line:90%
the default Nmap port range.

00:06:35.750 --> 00:06:38.930 align:middle line:84%
So it will scan 1,000 of the
most commonly used ports.

00:06:38.930 --> 00:06:41.930 align:middle line:84%
So I'll paste in the target
IP, and I'll hit Enter.

00:06:41.930 --> 00:06:44.330 align:middle line:84%
And this is going to
take a couple of seconds

00:06:44.330 --> 00:06:45.540 align:middle line:90%
to a couple of minutes.

00:06:45.540 --> 00:06:49.070 align:middle line:84%
So I'm just going to wait
for this to complete.

00:06:49.070 --> 00:06:52.010 align:middle line:84%
All right, so the
Nmap scan is complete,

00:06:52.010 --> 00:06:54.430 align:middle line:84%
and if we take a look
at these services that

00:06:54.430 --> 00:06:56.140 align:middle line:84%
are running on
the target system,

00:06:56.140 --> 00:07:00.760 align:middle line:84%
we can see that we have a
web server set up on port 80.

00:07:00.760 --> 00:07:02.800 align:middle line:84%
And the service
that's running on it

00:07:02.800 --> 00:07:07.930 align:middle line:84%
is the httpFileServer version
2.3 developed by rejetto So

00:07:07.930 --> 00:07:11.590 align:middle line:84%
let's try and identify whether
this particular service is

00:07:11.590 --> 00:07:12.910 align:middle line:90%
vulnerable to any exploits.

00:07:12.910 --> 00:07:16.090 align:middle line:84%
So I'll utilize
searchsploit, and I'll search

00:07:16.090 --> 00:07:18.740 align:middle line:90%
for rejetto right over here.

00:07:18.740 --> 00:07:21.280 align:middle line:84%
And we're looking
for version 2.3,

00:07:21.280 --> 00:07:23.950 align:middle line:84%
and it looks like
this specific version

00:07:23.950 --> 00:07:28.030 align:middle line:84%
is vulnerable to a command
execution vulnerability.

00:07:28.030 --> 00:07:31.090 align:middle line:84%
And luckily for us,
this specific version

00:07:31.090 --> 00:07:33.790 align:middle line:84%
has a Metasploit
module available

00:07:33.790 --> 00:07:36.490 align:middle line:84%
that will provide us with
a meterpreter session

00:07:36.490 --> 00:07:38.000 align:middle line:90%
upon execution.

00:07:38.000 --> 00:07:42.580 align:middle line:84%
So what we can do now is we
can start up MSF console,

00:07:42.580 --> 00:07:45.160 align:middle line:84%
and we can exploit
the target system.

00:07:45.160 --> 00:07:46.720 align:middle line:84%
Once we've gained
access, we can then

00:07:46.720 --> 00:07:49.450 align:middle line:84%
begin performing
local enumeration.

00:07:49.450 --> 00:07:51.430 align:middle line:84%
So we'll give this
a couple of seconds,

00:07:51.430 --> 00:07:54.880 align:middle line:84%
and I'll just run a
search for rejetto.

00:07:54.880 --> 00:07:55.480 align:middle line:90%
There we are.

00:07:55.480 --> 00:07:57.410 align:middle line:90%
And we'll use the exploit here.

00:07:57.410 --> 00:08:00.920 align:middle line:84%
So I'm going to copy that
there, and I'll say "use",

00:08:00.920 --> 00:08:02.430 align:middle line:90%
paste that in there.

00:08:02.430 --> 00:08:05.090 align:middle line:84%
And if we show the
options for this module,

00:08:05.090 --> 00:08:07.310 align:middle line:84%
the only option that we
need to change in our case

00:08:07.310 --> 00:08:09.170 align:middle line:84%
is the target IP,
which can be done

00:08:09.170 --> 00:08:11.280 align:middle line:90%
by setting the RHOST option.

00:08:11.280 --> 00:08:14.540 align:middle line:84%
So I'll copy the target
IP, and I'll just

00:08:14.540 --> 00:08:18.560 align:middle line:84%
say set RHOSTS and
paste in the target IP,

00:08:18.560 --> 00:08:21.230 align:middle line:90%
and we can type in exploit.

00:08:21.230 --> 00:08:23.060 align:middle line:84%
And we'll give this
a couple of seconds,

00:08:23.060 --> 00:08:26.600 align:middle line:84%
and that should provide us
with a meterpreter session.

00:08:26.600 --> 00:08:27.470 align:middle line:90%
There we are.

00:08:27.470 --> 00:08:28.715 align:middle line:90%
We get a meterpreter session.

00:08:28.715 --> 00:08:32.423 align:middle line:90%


00:08:32.423 --> 00:08:33.840 align:middle line:84%
So we'll give
that-- there we are.

00:08:33.840 --> 00:08:36.600 align:middle line:84%
So we've actually obtained
the meterpreter session now.

00:08:36.600 --> 00:08:40.110 align:middle line:84%
And we can begin performing
the local enumeration.

00:08:40.110 --> 00:08:42.510 align:middle line:84%
Now, I will not
be focusing on how

00:08:42.510 --> 00:08:45.630 align:middle line:84%
to automate local enumeration
with Metasploit framework

00:08:45.630 --> 00:08:47.500 align:middle line:90%
modules just yet.

00:08:47.500 --> 00:08:51.000 align:middle line:84%
We are primarily focused on how
to perform local enumeration

00:08:51.000 --> 00:08:54.550 align:middle line:84%
manually, which again, is a
very important skill to have.

00:08:54.550 --> 00:08:58.830 align:middle line:84%
Now, if you gain access to a
target system via meterpreter,

00:08:58.830 --> 00:09:00.540 align:middle line:84%
then you can obtain
the information

00:09:00.540 --> 00:09:03.540 align:middle line:84%
that we're looking for like
the operating system version

00:09:03.540 --> 00:09:06.120 align:middle line:90%
by typing in get user ID.

00:09:06.120 --> 00:09:08.850 align:middle line:84%
And that will, again,
tell you the current user.

00:09:08.850 --> 00:09:12.670 align:middle line:84%
And then we can say sysinfo
to obtain the host name.

00:09:12.670 --> 00:09:14.970 align:middle line:84%
So we can see that
the hostname is WIN,

00:09:14.970 --> 00:09:17.290 align:middle line:84%
and we have a
string of text here,

00:09:17.290 --> 00:09:21.000 align:middle line:84%
which means that the hostname
hasn't been explicitly set

00:09:21.000 --> 00:09:24.240 align:middle line:84%
by the user on this system
or the administrator.

00:09:24.240 --> 00:09:27.180 align:middle line:84%
We can get the operating
system edition, which

00:09:27.180 --> 00:09:30.810 align:middle line:84%
is Windows Server 2012, and the
build number and service pack.

00:09:30.810 --> 00:09:33.570 align:middle line:84%
So we can see that this is
running Windows Server 2012

00:09:33.570 --> 00:09:36.240 align:middle line:90%
R2 build 9600.

00:09:36.240 --> 00:09:39.870 align:middle line:84%
The target operating
system architecture is x64,

00:09:39.870 --> 00:09:44.760 align:middle line:84%
and we currently have a
32-bit meterpreter session.

00:09:44.760 --> 00:09:47.640 align:middle line:84%
If we take a look at the other
information like the domain,

00:09:47.640 --> 00:09:50.700 align:middle line:84%
we can see that it's part of
a standard Windows workgroup.

00:09:50.700 --> 00:09:55.380 align:middle line:84%
And the logged on users
are one or ourselves.

00:09:55.380 --> 00:09:58.530 align:middle line:84%
So that's how to enumerate that
information with meterpreter.

00:09:58.530 --> 00:10:01.120 align:middle line:84%
However, we are interested
in Windows commands.

00:10:01.120 --> 00:10:03.910 align:middle line:84%
So I'll open up a
command shell session.

00:10:03.910 --> 00:10:06.240 align:middle line:84%
So let's start off by
enumerating the hostname.

00:10:06.240 --> 00:10:09.000 align:middle line:84%
We can get that information
by typing in hostname.

00:10:09.000 --> 00:10:11.640 align:middle line:84%
And again, you can see we
get the same information

00:10:11.640 --> 00:10:14.550 align:middle line:84%
we would have got if we would
have typed in the sysinfo

00:10:14.550 --> 00:10:15.280 align:middle line:90%
command.

00:10:15.280 --> 00:10:17.880 align:middle line:84%
However, we're assuming that
you have a command shell

00:10:17.880 --> 00:10:20.760 align:middle line:84%
session as opposed to
a meterpreter session.

00:10:20.760 --> 00:10:23.970 align:middle line:84%
All right, so that is how
to obtain the hostname.

00:10:23.970 --> 00:10:27.240 align:middle line:84%
Now, there is a really,
really awesome Windows command

00:10:27.240 --> 00:10:30.210 align:middle line:84%
that allows you to enumerate
all information about the target

00:10:30.210 --> 00:10:31.000 align:middle line:90%
system.

00:10:31.000 --> 00:10:35.250 align:middle line:84%
So we can get that by
typing in systeminfo,

00:10:35.250 --> 00:10:38.070 align:middle line:84%
and that is different
than typing in sysinfo.

00:10:38.070 --> 00:10:39.700 align:middle line:90%
This is a Windows command.

00:10:39.700 --> 00:10:42.990 align:middle line:84%
So what this will display is
it'll display all the operating

00:10:42.990 --> 00:10:46.020 align:middle line:84%
system information,
like the edition,

00:10:46.020 --> 00:10:49.582 align:middle line:84%
the build number, as well as the
HotFixes or updates installed,

00:10:49.582 --> 00:10:51.040 align:middle line:84%
which are currently
displayed here.

00:10:51.040 --> 00:10:53.280 align:middle line:84%
So I'll just scroll to
the top of the results.

00:10:53.280 --> 00:10:56.730 align:middle line:84%
So you can see it'll display the
hostname, the operating system

00:10:56.730 --> 00:11:00.300 align:middle line:84%
name, the operating system
version, the operating system

00:11:00.300 --> 00:11:03.030 align:middle line:84%
manufacturer, the
configuration of the system.

00:11:03.030 --> 00:11:04.800 align:middle line:84%
You can see that
it's been configured

00:11:04.800 --> 00:11:06.870 align:middle line:90%
as a standalone server.

00:11:06.870 --> 00:11:11.740 align:middle line:84%
And you also obtain additional
information like the processor.

00:11:11.740 --> 00:11:13.740 align:middle line:84%
So you can see in
this case, it looks

00:11:13.740 --> 00:11:16.680 align:middle line:84%
like we have an Intel
Xeon processor here,

00:11:16.680 --> 00:11:19.200 align:middle line:90%
and it's running on Amazon AWS.

00:11:19.200 --> 00:11:21.730 align:middle line:84%
We can see the default
Windows directory,

00:11:21.730 --> 00:11:27.240 align:middle line:84%
which is on the C Windows
and the system32 directory.

00:11:27.240 --> 00:11:29.550 align:middle line:84%
And we can also identify
other information

00:11:29.550 --> 00:11:33.210 align:middle line:84%
like the boot device as
well as the system locale.

00:11:33.210 --> 00:11:34.890 align:middle line:84%
So that tells us
what language has

00:11:34.890 --> 00:11:38.460 align:middle line:84%
been configured on this target
system for the keyboard.

00:11:38.460 --> 00:11:40.920 align:middle line:84%
We also get
additional hardware or

00:11:40.920 --> 00:11:44.850 align:middle line:84%
resource-related information,
like the time zone.

00:11:44.850 --> 00:11:47.490 align:middle line:84%
And in regards to
the actual resources,

00:11:47.490 --> 00:11:50.470 align:middle line:84%
we can see that it tells us
the total physical memory.

00:11:50.470 --> 00:11:51.570 align:middle line:90%
So this is your RAM.

00:11:51.570 --> 00:11:54.000 align:middle line:84%
So the system has about
one gigabyte of RAM,

00:11:54.000 --> 00:11:58.750 align:middle line:84%
and the available
memory is 563 megabytes.

00:11:58.750 --> 00:12:01.890 align:middle line:84%
And then, of course, you have
your virtual memory allocations

00:12:01.890 --> 00:12:03.100 align:middle line:90%
right over there.

00:12:03.100 --> 00:12:05.430 align:middle line:84%
Now, the most important
piece of information

00:12:05.430 --> 00:12:08.260 align:middle line:84%
you can see right over here is
the domain, which in this case,

00:12:08.260 --> 00:12:11.110 align:middle line:84%
we can tell that it's not
part of any special domain.

00:12:11.110 --> 00:12:14.340 align:middle line:84%
We get the hostname, but
it comes under HotFixes.

00:12:14.340 --> 00:12:17.010 align:middle line:84%
So these are all the
HotFixes or updates

00:12:17.010 --> 00:12:19.530 align:middle line:84%
that have been installed on
this version of Windows that's

00:12:19.530 --> 00:12:21.240 align:middle line:90%
running on the target system.

00:12:21.240 --> 00:12:25.110 align:middle line:84%
And these HotFixes can actually
be copied and researched

00:12:25.110 --> 00:12:26.050 align:middle line:90%
on Google.

00:12:26.050 --> 00:12:28.350 align:middle line:84%
So all you need to do
is just copy this HotFix

00:12:28.350 --> 00:12:30.690 align:middle line:84%
and paste it in Google,
and it'll actually

00:12:30.690 --> 00:12:34.530 align:middle line:84%
tell you what this HotFix
was updating or patching.

00:12:34.530 --> 00:12:36.480 align:middle line:84%
And again, this
gives you an idea

00:12:36.480 --> 00:12:39.180 align:middle line:84%
of what updates
have been installed

00:12:39.180 --> 00:12:42.090 align:middle line:84%
and as a result
what vulnerabilities

00:12:42.090 --> 00:12:45.770 align:middle line:84%
this particular target
is vulnerable to.

00:12:45.770 --> 00:12:49.160 align:middle line:84%
At the bottom, you can see
it also displays the network

00:12:49.160 --> 00:12:50.040 align:middle line:90%
interfaces.

00:12:50.040 --> 00:12:52.880 align:middle line:84%
So you can see it actually
displays the network interface

00:12:52.880 --> 00:12:55.100 align:middle line:84%
name, the connection
type or name,

00:12:55.100 --> 00:12:59.330 align:middle line:84%
so ethernet 2, whether
DHCP is enabled,

00:12:59.330 --> 00:13:04.190 align:middle line:84%
the DHCP server IP address,
as well as the target system's

00:13:04.190 --> 00:13:07.160 align:middle line:90%
IPv4 and IPv6 address.

00:13:07.160 --> 00:13:10.020 align:middle line:84%
And in this case, it
tells us that right

00:13:10.020 --> 00:13:13.520 align:middle line:84%
of the on the Hyper-V that a
hypervisor has been detected.

00:13:13.520 --> 00:13:17.060 align:middle line:84%
And again, that just tells
you additional information

00:13:17.060 --> 00:13:19.940 align:middle line:84%
regarding the operating
system configuration.

00:13:19.940 --> 00:13:23.540 align:middle line:84%
So this command alone gives
you a lot of information

00:13:23.540 --> 00:13:26.190 align:middle line:90%
about the target system.

00:13:26.190 --> 00:13:28.520 align:middle line:84%
And in this case, this
is pertinent to Windows.

00:13:28.520 --> 00:13:30.980 align:middle line:84%
So we've already been
able to enumerate

00:13:30.980 --> 00:13:32.760 align:middle line:90%
quite a lot of information.

00:13:32.760 --> 00:13:35.330 align:middle line:84%
Now, there are a
few other commands

00:13:35.330 --> 00:13:38.630 align:middle line:84%
that you can utilize to
enumerate information

00:13:38.630 --> 00:13:43.520 align:middle line:84%
like the HotFixes, and we can
do that using the wmic utility

00:13:43.520 --> 00:13:44.540 align:middle line:90%
on Windows.

00:13:44.540 --> 00:13:50.820 align:middle line:84%
And we can say wmic qfe, and
we can then say get Caption,

00:13:50.820 --> 00:13:54.910 align:middle line:84%
and we can then specify
the description.

00:13:54.910 --> 00:13:57.620 align:middle line:90%
We can also specify HotFix ID.

00:13:57.620 --> 00:14:00.880 align:middle line:84%
So again, this will just
enumerate the installed updates

00:14:00.880 --> 00:14:02.980 align:middle line:90%
and the HotFix IDs.

00:14:02.980 --> 00:14:07.570 align:middle line:84%
And we can also specify another
important piece of information

00:14:07.570 --> 00:14:10.180 align:middle line:84%
that was not displayed with
the system info command,

00:14:10.180 --> 00:14:12.850 align:middle line:84%
and that is when the
updates were installed.

00:14:12.850 --> 00:14:15.760 align:middle line:84%
So we can do that by
saying installed on,

00:14:15.760 --> 00:14:17.855 align:middle line:90%
and we can hit Enter.

00:14:17.855 --> 00:14:19.480 align:middle line:84%
So we'll give this
a couple of seconds,

00:14:19.480 --> 00:14:21.220 align:middle line:84%
and now we get
additional information

00:14:21.220 --> 00:14:23.410 align:middle line:84%
regarding the updates
that were installed.

00:14:23.410 --> 00:14:26.740 align:middle line:84%
So the system info command will
just give you the HotFix IDs,

00:14:26.740 --> 00:14:32.500 align:middle line:84%
but the wmic utility can be used
to get additional information

00:14:32.500 --> 00:14:36.320 align:middle line:84%
like the actual caption,
which is the HotFix ID link.

00:14:36.320 --> 00:14:40.450 align:middle line:84%
So you now actually
have the ability to view

00:14:40.450 --> 00:14:43.090 align:middle line:84%
or learn more about a
particular HotFix ID.

00:14:43.090 --> 00:14:44.860 align:middle line:90%
You then get a description.

00:14:44.860 --> 00:14:47.530 align:middle line:84%
And in regards to
privilege escalation,

00:14:47.530 --> 00:14:51.970 align:middle line:84%
you're pretty much looking
for the security updates.

00:14:51.970 --> 00:14:54.700 align:middle line:84%
And you're not really
concerned with standard updates

00:14:54.700 --> 00:14:55.400 align:middle line:90%
like this.

00:14:55.400 --> 00:14:57.820 align:middle line:84%
And more importantly,
you also want

00:14:57.820 --> 00:14:59.830 align:middle line:84%
to know when this
was installed on

00:14:59.830 --> 00:15:01.940 align:middle line:90%
or the date it was installed on.

00:15:01.940 --> 00:15:04.870 align:middle line:84%
So you can see we have
another security update here.

00:15:04.870 --> 00:15:09.950 align:middle line:84%
These were all installed in
2014, so on and so forth.

00:15:09.950 --> 00:15:12.070 align:middle line:84%
So this is, again,
important information

00:15:12.070 --> 00:15:13.330 align:middle line:90%
that you should be aware of.

00:15:13.330 --> 00:15:17.050 align:middle line:84%
And you should actually be
able to enumerate manually

00:15:17.050 --> 00:15:22.780 align:middle line:84%
without relying on meterpreter
or commands like system info.

00:15:22.780 --> 00:15:26.800 align:middle line:84%
We can also enumerate the
actual operating system version

00:15:26.800 --> 00:15:30.220 align:middle line:84%
by navigating to the
root of the C drive.

00:15:30.220 --> 00:15:33.700 align:middle line:84%
And if we actually go back
into our meterpreter session,

00:15:33.700 --> 00:15:35.990 align:middle line:84%
we can navigate much
easier to that directory.

00:15:35.990 --> 00:15:46.520 align:middle line:84%
So I'll say cd C, and
under Windows and System32,

00:15:46.520 --> 00:15:51.410 align:middle line:84%
we should be able to identify
or find a file called eula.txt.

00:15:51.410 --> 00:15:54.380 align:middle line:84%
So I'll cat out the
contents of eula.txt.

00:15:54.380 --> 00:15:56.990 align:middle line:84%
In this case, it doesn't
exist, and again, it

00:15:56.990 --> 00:16:00.080 align:middle line:84%
might not exist on various
versions of Windows,

00:16:00.080 --> 00:16:02.780 align:middle line:84%
but that's another file
that can provide you

00:16:02.780 --> 00:16:06.260 align:middle line:84%
with information pertinent to
the operating system version.

00:16:06.260 --> 00:16:08.510 align:middle line:84%
And it'll also provide you
with additional information

00:16:08.510 --> 00:16:12.110 align:middle line:84%
like the build number
and the service pack.

00:16:12.110 --> 00:16:14.900 align:middle line:84%
So that really is
all that I wanted

00:16:14.900 --> 00:16:17.390 align:middle line:84%
to cover in this
particular video,

00:16:17.390 --> 00:16:21.590 align:middle line:84%
and that will conclude the
practical demonstration

00:16:21.590 --> 00:16:23.415 align:middle line:90%
side of this video.

00:16:23.415 --> 00:16:24.790 align:middle line:84%
All right, so now
that we've been

00:16:24.790 --> 00:16:27.200 align:middle line:84%
able to enumerate
system information

00:16:27.200 --> 00:16:29.170 align:middle line:84%
so we've been able to
get a lot of information

00:16:29.170 --> 00:16:32.710 align:middle line:84%
from the target, which again,
is very important during phases

00:16:32.710 --> 00:16:36.610 align:middle line:84%
like privilege escalation,
we can now turn our attention

00:16:36.610 --> 00:16:40.060 align:middle line:84%
to enumerating users and
groups and identifying

00:16:40.060 --> 00:16:43.510 align:middle line:84%
the various users
on a Windows system,

00:16:43.510 --> 00:16:47.350 align:middle line:84%
the groups available, the
members of a particular group,

00:16:47.350 --> 00:16:49.150 align:middle line:84%
as well as additional
information

00:16:49.150 --> 00:16:50.780 align:middle line:90%
pertinent to user accounts.

00:16:50.780 --> 00:16:54.500 align:middle line:84%
So I'll be seeing you
in the next video.

00:16:54.500 --> 00:16:55.000 align:middle line:90%