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

# Techniques du proxy Squid

## Proxys SQUID :

Si nous lançons une analyse sur le port 80, cela indique qu'il est **filtré** et non fermé :

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

### Méthode avec FoxyProxy

Voici le site normal où **rien n'apparaît**:

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

Nous créons un nouveau proxy avec **l'IP de la machine** et le port **3128**:

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

Avec **FoxyProxy**, le contenu apparaît :

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

### Méthode en ligne de commande :

Nous envoyons avec curl une requête au serveur web en utilisant le proxy de la machine via le port **3128**:

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

S'il demande **authentification**, faites-le comme suit :

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

## Reconnaissance des chemins (en passant par le proxy) :

Parfois, les **chemins n'apparaissent que** avec le proxy, voici un exemple de la façon de les voir :

```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/ace928f0c4cc7b64d09f1d3455bcb8d3afae8122" alt="" width="563"><figcaption></figcaption></figure>

## Script Python automatisé :

```python
#!/usr/bin/python3
import sys, signal, requests
def def_handler(sig, frame):
    print("/n/n[!] Exiting.../n")
    sys.exit(1)
# Techniques de proxy 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[+] Port " + str(tcp_port) + "- OUVERT")
if __name__ == '__main__':
    portDiscovery()

```

<figure><img src="/files/fb34182a32fad163b46aa3a47fe80751b0333433" 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/fr/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.
