pyLoader
Nmap Scan
$ nmap -sC -sV -p- --min-rate 10000 -Pn -oN nmap 192.168.194.26
Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-06-14 09:22 +08
Nmap scan report for 192.168.194.26
Host is up (0.0067s latency).
Not shown: 65533 closed tcp ports (conn-refused)
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 8.9p1 Ubuntu 3ubuntu0.1 (Ubuntu Linux; protocol 2.0)
| ssh-hostkey:
| 256 b9:bc:8f:01:3f:85:5d:f9:5c:d9:fb:b6:15:a0:1e:74 (ECDSA)
|_ 256 53:d9:7f:3d:22:8a:fd:57:98:fe:6b:1a:4c:ac:79:67 (ED25519)
9666/tcp open http CherryPy wsgiserver
|_http-server-header: Cheroot/8.6.0
| http-robots.txt: 1 disallowed entry
|_/
| http-title: Login - pyLoad
|_Requested resource was /login?next=http://192.168.194.26:9666/
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 39.55 secondsInitial Access
Port 9666
After looking at the nmap results, we will first look at port 9666.
After searching online on what this service does, we can see this.

After going into the webpage, it will bring us to a login page.

We can try the usual password but it does not work. However searching online if there is any default credentials, turns out there are default credential for this service.

After login in using those credentials, we are at this page.

When we click on info on the top right corner of the webpage, we can see the version of the OS, python and pyLoad that the service is using.

CVE-2023-0297
After searching online for any potential exploit for pyLoad, there is 1 result that was returned.
It was a pre-auth RCE exploit.
We will first download the payload
The content of the exploit is shown below
We will test if the exploit is working.
First, we will run this to watch for the traffic. (tun0 is my interface for vpn, might be different from others)
Then, we will execute the exploit
We can see the ICMP echo request and reply. This means the exploit is working as intended.
So, now we will try to call a reverse shell using that exploit.

After a while, we got back a reverse shell.

This shell just so happens to be root also.
Last updated