[Tut] Road Walkthrough TryHackMe – A Black Box Pentesting Challenge

[Tut] Road Walkthrough TryHackMe – A Black Box Pentesting Challenge - Printable Version

+- Sick Gaming (https://sickgaming.net)
+-- Forum: Programming (https://sickgaming.net/forum-76.html)
+--- Forum: Python (https://sickgaming.net/forum-83.html)
+--- Thread: [Tut] Road Walkthrough TryHackMe – A Black Box Pentesting Challenge (/thread-100723.html)

[Tut] Road Walkthrough TryHackMe – A Black Box Pentesting Challenge - xSicKxBot - 02-09-2023

Road Walkthrough TryHackMe – A Black Box Pentesting Challenge

5/5 – (1 vote)

[Image: lyteCache.php?origThumbUrl=https%3A%2F%2...efault.jpg]

CHALLENGE OVERVIEW

Link: https://tryhackme.com/room/road
Difficulty: Medium
Target: user/root flags
Highlights: retrieving user credentials from a Mongo DB, privilege escalation by exploiting a glitch in the
Code:
pkexec
bin
Tools used:
Code:
nmap
,
Code:
dirb
,
Code:
burpsuite
Tags: pentesting, security, mongoDB, SSH

BACKGROUND

What is black box pentesting?

[Image: image-139.png]

The term black box refers to a challenge where only the target machine IP is known to the penetration tester. Nothing else about the server is disclosed to the attacker, so everything must be discovered during the enumeration stage.

On the other end of the spectrum is white box pentesting, where information about the internal workings of a server is shared with the pentester.

ENUMERATION/RECON

[Image: image-140.png]

Let’s kick things off with some standard

Code:
nmap

and

Code:
dirb

scans.

Code:
sudo nmap -p- -A $targetIP -O -o /home/kalisurfer/THM/road-walkthrough/nmap.txt

It looks like they are running SSH and HTTP services. No surprises here!

Code:
dirb http://$targetIP

Our

Code:
dirb

scan sniffed out a few interesting directories:

Code:
/assets

Code:
/phpMyAdmin/ChangeLog

and

Code:
/v2

. We’ll look into each of these in more detail.

INVESTIGATING /phpMyAdmin

We discover a login portal at

Code:
/phpMyAdmin/index.php

INVESTIGATING /assets

When we browse the changelogs, we can identify the version number (5.1.0) for phpMyAdmin.

We also find a link to a Git repo with changelogs going back all the way to the year 2000!

This is a potential treasure trove of interesting information. We’ll check

Code:
exploit-db

to see if there are any known vulnerabilities. There are a bunch, but nothing for version 5.1.0.

For now, let’s move on.

[Image: image-131.png]

INVESTIGATING /v2

We discover another login portal

Code:
/v2/admin/login.html

. This one has a register option, so we can go ahead and create a new user and see what else we can view from within a standard user account.

[Image: image-129.png]

INITIAL FOOTHOLD

[Image: image-141.png]

We pivoted from our new user to the admin account by intercepting the TCP request to change the password using

Code:
burpsuite

and modifying the parameters to the admin’s email address before forwarding the request.

After successfully changing it to the admin’s password, we can login as admin with our new password and upload a revshell via the profile pic upload option.

[Image: image-128-1024x387.png]

From our admin dashboard, let’s go ahead and upload a revshell (from PHP pentest monkey, naming it

Code:
revshell.php

), start up a

Code:
netcat

listener on the corresponding port, and finally trigger it by loading the following address in our browser.

Code:
http://10.10.154.107/v2/profileimages/revshell.php

We caught the revshell and now we have our initial foothold!

EXTRACTING USER CREDENTIALS FROM MONGO DB

[Image: image-127.png]

And now we have user

Code:
webdeveloper

’s password in plaintext from Mongo DB! We can use “

Code:
su webdeveloper

” to switch users with our new password.

LOCAL RECON

[Image: image-142.png]

We easily found our first flag,

Code:
user.txt

, in the

Code:
/home/webdeveloper

directory.

Code:
63—-omitted—---45

After uploading Linpeas to the target machine via a python3 simple HTTP server, let’s run it and analyze the results.

[Image: image-124.png]

The first CVE is the one we will use to privesc. Instead of using the three file method that is outlined on

Code:
exploit-db

, we’ll do it manually using two terminals logged in as

Code:
webuser

Let’s also check sudo privileges.

[Image: image-122.png]

The

Code:
LD_PRELOAD

and

Code:
sky_backup_utility

are both interesting findings. We’ll save these for later in case we hit a dead end with CVE 2021-4034.

PRIV-ESC

[Image: image-143.png]

We’ll execute privilege escalation by exploiting a glitch in the

Code:
pkexec bin

(policykit vulnerability – cve-2021-4034). Open a second shell as

Code:
webdeveloper

.

Issue the following commands one-by-one in the corresponding terminals.

Terminal 1 |
Terminal 2

Code:
echo $$

|

|

Code:
pkttyagent --process <number of the process ID from echo $$>

Code:
pkexec "/bin/bash"

|

|
password for

Code:
webdeveloper

(recieve the root shell in terminal 1) |

POST-EXPLOITATION

Let’s grab the root flag:

[Image: image-137.png]

FINAL THOUGHTS

[Image: image-144.png]

This box was fairly challenging and really pushed me to take careful notes about my findings during enumeration and also to thoughtfully plan my strategy for gaining the initial foothold and for the priv-esc stage.

These more advanced boxes are forcing me to start putting together longer sequences of hacking tricks that were used more in isolation on the easier boxes.