> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/ports-and-services/devzat-8443.md).
# Devzat - 8443
Devzat file parameter abuse, backup discovery, path traversal, shadow file read, and root SSH key access.
### Port 8443 (Devzat - Production)
Port 8443 exposes a production Devzat instance. The `file` parameter can list files on the system as root, but this feature is password protected.
Trying *catherine*'s password fails. Search for files that *catherine* can read on the system.
### Search for files readable by Catherine
Find all files readable by *catherine*:
```bash
find / -user catherine -readable 2>/dev/null | grep -vE "cgroup|proc"
```
Two backup `.zip` files are found:
* `/var/backups/devzat-main.zip`
* `/var/backups/devzat-dev.zip`
Download the backup file `devzat-dev.zip` and filter its contents for passwords. A useful password is found: **`CeilingCatStillAThingIn2021?`**.
Use this password to access `/etc/shadow` through the `file` parameter:
```bash
/file /etc/shadows CeilingCatStillAThingIn2021?
```
Although the password is correct, **path traversal** is required to gain full access. Use traversal to navigate the file system:
```bash
/file ../../../../etc/shadow CeilingCatStillAThingIn2021?
```
The `/etc/shadow` file is successfully displayed as root.
### SSH access as root
Use an additional path traversal to access root's SSH key:
```bash
/file ../../../../root/.ssh/id_rsa CeilingCatStillAThingIn2021?
```
Download the SSH key and log in 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/ports-and-services/devzat-8443.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 `automate deployments from our CI pipeline` 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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)