WEBVTT

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


00:00:03.437 --> 00:00:05.401 align:middle line:90%
[ELECTRONIC NOISES]

00:00:05.401 --> 00:00:10.160 align:middle line:90%


00:00:10.160 --> 00:00:13.940 align:middle line:84%
Now we're going to introduce the
Microsoft, most common version

00:00:13.940 --> 00:00:16.070 align:middle line:90%
of an SQL Server, MSSQL.

00:00:16.070 --> 00:00:20.870 align:middle line:90%


00:00:20.870 --> 00:00:23.075 align:middle line:84%
In our environment,
we've got our IP address.

00:00:23.075 --> 00:00:26.630 align:middle line:90%


00:00:26.630 --> 00:00:30.150 align:middle line:84%
We run an Nmap scan, and we
see we're up against probably

00:00:30.150 --> 00:00:33.080 align:middle line:90%
a Microsoft system.

00:00:33.080 --> 00:00:37.410 align:middle line:90%
It's also running port 1433.

00:00:37.410 --> 00:00:46.520 align:middle line:84%
If we do a service
enumeration scan, we get back

00:00:46.520 --> 00:00:49.300 align:middle line:84%
the latest version
of the software,

00:00:49.300 --> 00:00:55.510 align:middle line:90%
Microsoft SQL Server 2019.

00:00:55.510 --> 00:01:03.430 align:middle line:84%
We can double down on that and
run a script for ms-sql-info.

00:01:03.430 --> 00:01:07.550 align:middle line:90%


00:01:07.550 --> 00:01:09.780 align:middle line:90%
That'll give us a little more.

00:01:09.780 --> 00:01:11.010 align:middle line:90%
We have the service.

00:01:11.010 --> 00:01:13.770 align:middle line:84%
We've got the number,
the exact version.

00:01:13.770 --> 00:01:17.970 align:middle line:84%
And it could tell us the
various service pack.

00:01:17.970 --> 00:01:20.498 align:middle line:90%
Patches applied, it says false.

00:01:20.498 --> 00:01:22.290 align:middle line:84%
If we don't know what
that means right now,

00:01:22.290 --> 00:01:23.548 align:middle line:90%
we can look it up later.

00:01:23.548 --> 00:01:25.590 align:middle line:84%
But currently, we just
want to enumerate and pull

00:01:25.590 --> 00:01:26.925 align:middle line:90%
as much information as we can.

00:01:26.925 --> 00:01:34.400 align:middle line:90%


00:01:34.400 --> 00:01:36.520 align:middle line:84%
The next thing we can
look into is ntlm-info.

00:01:36.520 --> 00:01:39.920 align:middle line:90%


00:01:39.920 --> 00:01:48.110 align:middle line:84%
And with this, we need
some arguments to tell it

00:01:48.110 --> 00:01:54.131 align:middle line:90%
which instance to look at.

00:01:54.131 --> 00:01:56.330 align:middle line:90%
We want 1433.

00:01:56.330 --> 00:02:00.110 align:middle line:84%
And we got the target name of
MSSQL-SERVER, NetBIOS domain

00:02:00.110 --> 00:02:03.920 align:middle line:90%
name of MSSQL-SERVER.

00:02:03.920 --> 00:02:05.045 align:middle line:90%
We'll store that for later.

00:02:05.045 --> 00:02:11.710 align:middle line:90%


00:02:11.710 --> 00:02:19.570 align:middle line:84%
Another script we can run is
an MSSQL brute force, so brute.

00:02:19.570 --> 00:02:22.310 align:middle line:90%


00:02:22.310 --> 00:02:26.310 align:middle line:84%
And the arguments for this one
are going to be our word lists.

00:02:26.310 --> 00:02:34.760 align:middle line:84%
So for our user, userdb=, we
have these on our desktop,

00:02:34.760 --> 00:02:38.420 align:middle line:90%
wordlist, common_users.

00:02:38.420 --> 00:02:41.945 align:middle line:90%


00:02:41.945 --> 00:02:42.820 align:middle line:90%
And then the passdb--

00:02:42.820 --> 00:02:48.800 align:middle line:90%


00:02:48.800 --> 00:02:49.410 align:middle line:90%
very similar.

00:02:49.410 --> 00:03:01.278 align:middle line:90%


00:03:01.278 --> 00:03:02.070 align:middle line:90%
And we'll run that.

00:03:02.070 --> 00:03:04.200 align:middle line:90%
And it will brute force.

00:03:04.200 --> 00:03:07.410 align:middle line:84%
Again, the arguments for the
different scripts that we run

00:03:07.410 --> 00:03:10.770 align:middle line:84%
are going to be
based on the script.

00:03:10.770 --> 00:03:12.900 align:middle line:84%
Whoever was writing
those scripts

00:03:12.900 --> 00:03:15.240 align:middle line:84%
determines what the
variables are called.

00:03:15.240 --> 00:03:21.450 align:middle line:84%
We came back with auditor and
jasmine1, dbadmin and bubbles1,

00:03:21.450 --> 00:03:24.810 align:middle line:90%
and admin and annamaria.

00:03:24.810 --> 00:03:27.460 align:middle line:84%
We'll take advantage of
that in just a second.

00:03:27.460 --> 00:03:31.530 align:middle line:84%
Let's see if there's
any empty passwords.

00:03:31.530 --> 00:03:40.140 align:middle line:84%
ms-sql-empty-password
and we get one,

00:03:40.140 --> 00:03:43.992 align:middle line:84%
username sa with
an empty password.

00:03:43.992 --> 00:03:45.575 align:middle line:84%
We could enumerate
that a little more.

00:03:45.575 --> 00:03:48.310 align:middle line:90%


00:03:48.310 --> 00:03:52.480 align:middle line:84%
Well, let's take advantage
of that Maria password

00:03:52.480 --> 00:03:53.950 align:middle line:90%
we came across.

00:03:53.950 --> 00:04:02.790 align:middle line:84%
We will run a query,
pass in some arguments,

00:04:02.790 --> 00:04:04.345 align:middle line:90%
the username of admin.

00:04:04.345 --> 00:04:09.025 align:middle line:90%


00:04:09.025 --> 00:04:11.040 align:middle line:90%
The password was annamaria--

00:04:11.040 --> 00:04:18.360 align:middle line:90%


00:04:18.360 --> 00:04:19.125 align:middle line:90%
query.query.

00:04:19.125 --> 00:04:26.200 align:middle line:90%


00:04:26.200 --> 00:04:30.514 align:middle line:84%
And we will select everything
from master..syslogins.

00:04:30.514 --> 00:04:35.930 align:middle line:90%


00:04:35.930 --> 00:04:37.970 align:middle line:84%
And this one, because
it's a weird output

00:04:37.970 --> 00:04:39.650 align:middle line:84%
we're going to
output it as normal,

00:04:39.650 --> 00:04:43.490 align:middle line:90%
oN, and call it output.text.

00:04:43.490 --> 00:04:47.150 align:middle line:84%
And I'll show you what that
looks like in a second.

00:04:47.150 --> 00:04:50.480 align:middle line:84%
Let me correct the
syntax near the star.

00:04:50.480 --> 00:04:52.580 align:middle line:84%
Let's go with
select, not "slect."

00:04:52.580 --> 00:04:55.900 align:middle line:90%


00:04:55.900 --> 00:05:00.490 align:middle line:84%
It gave us this database
output, which is a mess.

00:05:00.490 --> 00:05:06.636 align:middle line:84%
What we can do, if we go into
root and look at output.txt,

00:05:06.636 --> 00:05:08.650 align:middle line:90%
it made this full size.

00:05:08.650 --> 00:05:14.380 align:middle line:90%
And we have wordwrap turned off.

00:05:14.380 --> 00:05:19.450 align:middle line:84%
We can come in and see it in a
little easier-to-read fashion.

00:05:19.450 --> 00:05:21.670 align:middle line:84%
It's a database, so
there's a lot of columns

00:05:21.670 --> 00:05:24.300 align:middle line:90%
and a lot of rows.

00:05:24.300 --> 00:05:26.460 align:middle line:84%
It could be even
worse potentially.

00:05:26.460 --> 00:05:29.820 align:middle line:84%
But some of the logins
are these services.

00:05:29.820 --> 00:05:34.050 align:middle line:84%
There are nt services,
which are more helpful.

00:05:34.050 --> 00:05:35.280 align:middle line:90%
That's our machine services.

00:05:35.280 --> 00:05:40.530 align:middle line:84%
And then it looks like there
are some individual user logins.

00:05:40.530 --> 00:05:44.175 align:middle line:84%
There's this BUILTIN user and NT
AUTHORITY SYSTEM also accessed.

00:05:44.175 --> 00:05:48.000 align:middle line:90%


00:05:48.000 --> 00:05:51.160 align:middle line:84%
We can come back to this
and see what's useful later.

00:05:51.160 --> 00:05:54.087 align:middle line:84%
For now, we're
enumerating, so we gather,

00:05:54.087 --> 00:05:55.045 align:middle line:90%
gather, gather, gather.

00:05:55.045 --> 00:05:59.860 align:middle line:90%


00:05:59.860 --> 00:06:01.320 align:middle line:84%
Once you're done
gathering, then we

00:06:01.320 --> 00:06:06.250 align:middle line:84%
can go back and
see what is useful.

00:06:06.250 --> 00:06:07.350 align:middle line:90%
Let's dump some hashes.

00:06:07.350 --> 00:06:11.620 align:middle line:90%


00:06:11.620 --> 00:06:20.340 align:middle line:84%
That's another useful thing
to do because dumping hashes

00:06:20.340 --> 00:06:21.300 align:middle line:90%
usually gets us--

00:06:21.300 --> 00:06:25.170 align:middle line:90%


00:06:25.170 --> 00:06:26.460 align:middle line:90%
we can use hashes.

00:06:26.460 --> 00:06:34.500 align:middle line:84%
We can pass a hash,
which would let

00:06:34.500 --> 00:06:37.020 align:middle line:84%
us access other machines
without necessarily

00:06:37.020 --> 00:06:38.400 align:middle line:90%
having the password.

00:06:38.400 --> 00:06:41.690 align:middle line:90%


00:06:41.690 --> 00:06:43.190 align:middle line:84%
I mean, we do have
passwords here.

00:06:43.190 --> 00:06:50.630 align:middle line:84%
But maybe there's stuff that
didn't come with a password.

00:06:50.630 --> 00:06:55.730 align:middle line:84%
There's more accounts than
the few that we had before

00:06:55.730 --> 00:06:58.220 align:middle line:90%
and some hashes to go with them.

00:06:58.220 --> 00:07:03.731 align:middle line:84%
We saw this
MS_PolicyEventProcessingLogin

00:07:03.731 --> 00:07:06.330 align:middle line:90%
in that output.

00:07:06.330 --> 00:07:08.330 align:middle line:84%
I don't know what we can
deal with it right now.

00:07:08.330 --> 00:07:09.430 align:middle line:90%
But it's useful to have.

00:07:09.430 --> 00:07:13.370 align:middle line:90%


00:07:13.370 --> 00:07:20.785 align:middle line:84%
You never want to count things
out in your enumeration phase.

00:07:20.785 --> 00:07:26.300 align:middle line:90%


00:07:26.300 --> 00:07:31.525 align:middle line:84%
Let's see if we can
run some actual code.

00:07:31.525 --> 00:07:37.180 align:middle line:90%


00:07:37.180 --> 00:07:39.670 align:middle line:90%
We need a username.

00:07:39.670 --> 00:07:51.000 align:middle line:84%
We will use admin
and annamaria again.

00:07:51.000 --> 00:07:53.475 align:middle line:84%
And then what do we actually
want to ask it to do?

00:07:53.475 --> 00:08:01.740 align:middle line:90%


00:08:01.740 --> 00:08:04.485 align:middle line:84%
The command, we'll have
it run as ipconfig.

00:08:04.485 --> 00:08:09.710 align:middle line:90%


00:08:09.710 --> 00:08:14.880 align:middle line:84%
We get back the IP
address of the machine.

00:08:14.880 --> 00:08:17.330 align:middle line:84%
This default gateway
could be useful to us.

00:08:17.330 --> 00:08:19.520 align:middle line:84%
We might want to be
using that later to see

00:08:19.520 --> 00:08:20.690 align:middle line:90%
what sort of connections.

00:08:20.690 --> 00:08:22.580 align:middle line:84%
But really, what's
helpful is we were

00:08:22.580 --> 00:08:26.060 align:middle line:84%
able to run a command in
a shell on their machine

00:08:26.060 --> 00:08:29.330 align:middle line:90%
remotely utilizing SQL.

00:08:29.330 --> 00:08:31.430 align:middle line:90%
We saw that before with MySQL.

00:08:31.430 --> 00:08:38.059 align:middle line:84%
Now we can do it with MSSQL,
which can be quite handy.

00:08:38.059 --> 00:08:42.260 align:middle line:84%
In this situation now
instead of an ipconfig,

00:08:42.260 --> 00:08:47.510 align:middle line:84%
let's have it do type, which
is the Windows version of cat

00:08:47.510 --> 00:08:54.410 align:middle line:84%
if you're more familiar with
Linux than you are Windows.

00:08:54.410 --> 00:08:56.640 align:middle line:90%
Let's have it read a file.

00:08:56.640 --> 00:08:59.990 align:middle line:84%
So on the C drive, there
was a file flag.txt.

00:08:59.990 --> 00:09:02.130 align:middle line:84%
And we got the
output of that file,

00:09:02.130 --> 00:09:03.380 align:middle line:90%
which was a hash in this case.

00:09:03.380 --> 00:09:11.360 align:middle line:90%


00:09:11.360 --> 00:09:16.090 align:middle line:84%
It's useful to know how to
enumerate multiple systems.

00:09:16.090 --> 00:09:19.060 align:middle line:84%
If you come across
another version of SQL,

00:09:19.060 --> 00:09:22.510 align:middle line:84%
we could go into NSE, go
on the website for Nmap,

00:09:22.510 --> 00:09:25.720 align:middle line:84%
and see what other scripts
apply in those situations.

00:09:25.720 --> 00:09:27.880 align:middle line:84%
That's how you would do
this enumeration thing.

00:09:27.880 --> 00:09:30.130 align:middle line:84%
If you see something
that isn't covered here,

00:09:30.130 --> 00:09:32.500 align:middle line:84%
then you at least
have an idea of,

00:09:32.500 --> 00:09:34.150 align:middle line:90%
what should we be looking for?

00:09:34.150 --> 00:09:35.470 align:middle line:90%
What should we be trying?

00:09:35.470 --> 00:09:38.190 align:middle line:84%
That's what we're
trying to do here.

00:09:38.190 --> 00:09:39.000 align:middle line:90%