> 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-vulnerabilities/proxys-squid-attack/proxys-squid-techniques-pentesting-web.md).

# Técnicas de Proxy Squid

## Proxies SQUID:

Se fizermos uma varredura na porta 80, isso indica que ela está **filtrada** e não fechada:

<figure><img src="/files/29452956dccd5ff9b855a8bd5a089c54af42f347" alt="" width="563"><figcaption></figcaption></figure>

### Método com um FoxyProxy

Aqui está o site normal onde **nada aparece**:

<figure><img src="/files/ef5d98811eb2785688fe8b456b5763ef7715adba" alt="" width="560"><figcaption></figcaption></figure>

Nós criamos um novo proxy com o **IP da máquina** e porta **3128**:

<figure><img src="/files/3f96816fee00f6fd96b8891be494f00d6672129c" alt="" width="563"><figcaption></figcaption></figure>

Com **FoxyProxy**, o conteúdo aparece:

<figure><img src="/files/88788cb003860e48b41ea2f46e81fd0fac3ab7d9" alt="" width="563"><figcaption></figcaption></figure>

### Método na linha de comando:

Enviamos com curl uma requisição ao servidor web usando o proxy da máquina pela porta **3128**:

<figure><img src="/files/2ec7bc4175f43d31a51d8914f1b6a358e07b7b5d" alt="" width="562"><figcaption></figcaption></figure>

Se pedir **autenticação**, faça da seguinte forma:

<figure><img src="/files/d7724cd184819b7bce593693a501155c3aea7d43" alt="" width="563"><figcaption></figcaption></figure>

## Reconhecimento de caminhos (passando pelo proxy):

Às vezes, os **caminhos só aparecem** com o proxy, aqui está um exemplo de como vê-los:

```bash
gobuster dir -u http://192.168.71.131/ --proxy http://192.168.71.131:3128 -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 20

```

<figure><img src="/files/b077ba08cb6552a1d5c2a1987eab68ea14878a2d" alt="" width="563"><figcaption></figcaption></figure>

## Script Python automatizado:

```python
#!/usr/bin/python3
import sys, signal, requests
def def_handler(sig, frame):
    print("/n/n[!] Exiting.../n")
    sys.exit(1)
# Técnicas de Proxy do Squid
signal.signal(signal.SIGINT, def_handler)
main_url = "http://127.0.0.1"
squid_proxy = {'http': 'http://192.168.71.131:3128'}
def portDiscovery():
    common_tcp_port= {21, 22, 23, 25, 53, 80, 110, 111, 135, 139, 143, 443, 445, 993, 995, 1723, 3306, 3389, 5900, 8080, 8443, 8888, 5900, 6666, 6667, 6668, 6669, 7000, 10000, 32768, 32769, 32770, 32771, 32772, 32773, 32774, 32775, 32776, 32777, 32778, 32779, 49152, 49153, 49154, 49155, 49156, 49157, 49158, 49159, 49160, 49161, 49162}
    for tcp_port in common_tcp_port:
        r = requests.get(main_url + ':' + str(tcp_port), proxies=squid_proxy)
        if r.status_code != 503:
            print("/n[+] Porta " + str(tcp_port) + " - ABERTA")
if __name__ == '__main__':
    portDiscovery()

```

<figure><img src="/files/917223870df356ac49e4bf91b3a8c807085575e2" alt="" width="563"><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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/pt-br/web-vulnerabilities/proxys-squid-attack/proxys-squid-techniques-pentesting-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
