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

# Squid-Proxy-Techniken

## SQUID-Proxys:

Wenn wir einen Scan auf Port 80 durchführen, zeigt dies an, dass es **gefiltert** und nicht geschlossen:

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

### Methode mit FoxyProxy

Hier ist die normale Website, auf der **nichts erscheint**:

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

Wir erstellen einen neuen Proxy mit der **IP der Maschine** und Port **3128**:

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

Mit **FoxyProxy**, erscheint der Inhalt:

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

### Methode in der Kommandozeile:

Wir senden mit curl eine Anfrage an den Webserver unter Verwendung des Proxys der Maschine über Port **3128**:

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

Falls nach **Authentifizierung**, führen Sie sie wie folgt durch:

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

## Aufklärung von Pfaden (über den Proxy):

Manchmal **erscheinen die Pfade nur** mit dem Proxy, hier ist ein Beispiel, wie man sie sehen kann:

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

## Automatisiertes Python-Skript:

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

```

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