> 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-dog.md).
# HTB - Dog
## Enumeration and Foothold
### NMAP
```bash
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 8.2p1 Ubuntu 4ubuntu0.12 (Ubuntu Linux; protocol 2.0)
80/tcp open http Apache httpd 2.4.41 ((Ubuntu))
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
```
### HTTP
clicking on dog obesity results in the below url request
the parameter q references local files directly could be a good opportunity to look for LFI
no LFI but there is also a login page.
weak credentials like `admin : admin` do not work here.
directory enumeration revealed a git directory.
i can dump the git directory locally and investigate
found database credentials in the settings.php of the gitdumper files
using the discovered credentials tried to login but they did not work. so i need o find a user who can be able to be used to use the password.
that said grepping the git repo for users revealed a user name
now that i have username, i can try the discovered password to against this user to try logging in.
and we got successful authentication.
tiffany is a administrative user. also the version of cms being used is 1.27.1
poking around google the cms is vulnerable to Authenticated RCE.
{% embed url="" %}
The above poc explains the exploitation steps.
the exploitation involves writing a php shell into a modules directory by zip uploads.
it takes tar file as upload form so i can upload a shell.tar here.
found this page which has the tar file to exploit
{% embed url="" %}
there is a shell.php in the tar file, that said i will upload the file to target to get shell access.
the code execution is confirmed with that i will try to get a reverse shell.
## Shell as www-data
next i will try to upgrade the shell
## Shell as Johncusack
using the same password obtained from git repo got access as john, as he is using the same password as tiffany.
johncusack can run bee as root without password.
{% embed url="" %}
GTFObins has page on how to exploit this binary
### bee privilege escalation
root path confirmed.
now we can get shell as root
## Shell as Root
```bash
johncusack@dog:~$ sudo /usr/local/bin/bsudo /usr/local/bin/bee --root=/var/www/html eval 'system("/bin/bash -p");'
sudo /usr/local/bin/bee --root=/var/www/html eval 'system("/bin/bash -p");'
root@dog:/var/www/html#
```
---
# 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-dog.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.
