GitBook: [master] 5 pages and 10 assets modified
Before Width: | Height: | Size: 341 KiB After Width: | Height: | Size: 341 KiB |
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
@ -284,6 +284,7 @@
|
|||
* [631 - Internet Printing Protocol\(IPP\)](pentesting/pentesting-631-internet-printing-protocol-ipp.md)
|
||||
* [873 - Pentesting Rsync](pentesting/873-pentesting-rsync.md)
|
||||
* [1026 - Pentesting Rusersd](pentesting/1026-pentesting-rusersd.md)
|
||||
* [1080 - Pentesting Socks](pentesting/1080-pentesting-socks.md)
|
||||
* [1098/1099 - Pentesting Java RMI](pentesting/1099-pentesting-java-rmi.md)
|
||||
* [1433 - Pentesting MSSQL - Microsoft SQL Server](pentesting/pentesting-mssql-microsoft-sql-server.md)
|
||||
* [1521,1522-1529 - Pentesting Oracle TNS Listener](pentesting/1521-1522-1529-pentesting-oracle-listener/README.md)
|
||||
|
|
|
@ -127,7 +127,7 @@ The files in the folder WPDNSE are a copy of the original ones, then won't survi
|
|||
|
||||
Check the file `C:\Windows\inf\setupapi.dev.log` to get the timestamps about when the USB connection was produced \(search for `Section start`\).
|
||||
|
||||
![](../../../.gitbook/assets/image%20%28490%29.png)
|
||||
![](../../../.gitbook/assets/image%20%28477%29%20%281%29.png)
|
||||
|
||||
### USB Detective
|
||||
|
||||
|
@ -217,7 +217,7 @@ Having these files you can sue the tool [**Rifiuti**](https://github.com/abelche
|
|||
.\rifiuti-vista.exe C:\Users\student\Desktop\Recycle
|
||||
```
|
||||
|
||||
![](../../../.gitbook/assets/image%20%28495%29.png)
|
||||
![](../../../.gitbook/assets/image%20%28495%29%20%281%29.png)
|
||||
|
||||
## Programs Executed
|
||||
|
||||
|
|
|
@ -135,7 +135,7 @@ Within this registry it's possible to find:
|
|||
|
||||
![](../../../.gitbook/assets/image%20%28489%29.png)
|
||||
|
||||
![](../../../.gitbook/assets/image%20%28481%29.png)
|
||||
![](../../../.gitbook/assets/image%20%28479%29%20%281%29.png)
|
||||
|
||||
Moreover, checking the registry `HKLM\SYSTEM\ControlSet001\Enum\USB` and comparing the values of the sub-keys it's possible to find the VID value
|
||||
|
||||
|
@ -157,7 +157,7 @@ Having the **{GUID}** of the device it's now possible to **check all the NTUDER.
|
|||
|
||||
Checking the registry `System\MoutedDevices` it's possible to find out **which device was the last one mounted**. In the following image check how the last device mounted in `E:` is the Thoshiba one \(using the tool Registry Explorer\).
|
||||
|
||||
![](../../../.gitbook/assets/image%20%28483%29.png)
|
||||
![](../../../.gitbook/assets/image%20%28483%29%20%281%29.png)
|
||||
|
||||
### Volume Serial Number
|
||||
|
||||
|
|
|
@ -593,7 +593,7 @@ Many apps log informative \(and potentially sensitive\) messages to the console
|
|||
5. Reproduce the problem.
|
||||
6. Click on the **Open Console** button located in the upper right-hand area of the Devices window to view the console logs on a separate window.
|
||||
|
||||
![](../../.gitbook/assets/image%20%28466%29.png)
|
||||
![](../../.gitbook/assets/image%20%28466%29%20%281%29.png)
|
||||
|
||||
You can also connect to the device shell as explained in Accessing the Device Shell, install **socat** via **apt-get** and run the following command:
|
||||
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
# 1080 - Pentesting Socks 4/5
|
||||
# 1080 - Pentesting Socks
|
||||
|
||||
## Basic Information
|
||||
|
||||
SOCKS is an Internet protocol that exchanges network packets between a client and server through a proxy server. SOCKS5 optionally provides authentication,
|
||||
SOCKS is an Internet protocol that exchanges network packets between a client and server through a proxy server. SOCKS5 optionally provides authentication,
|
||||
so only authorized users may access a server.
|
||||
|
||||
Practically, a SOCKS server proxies TCP connections to an arbitrary IP address, and provides a means for UDP packets to be forwarded.
|
||||
SOCKS performs at Layer 5 of the OSI model
|
||||
Practically, a SOCKS server proxies TCP connections to an arbitrary IP address, and provides a means for UDP packets to be forwarded.
|
||||
SOCKS performs at Layer 5 of the OSI model
|
||||
|
||||
**Default Port:** 1080
|
||||
|
||||
|
@ -18,20 +18,23 @@ SOCKS performs at Layer 5 of the OSI model
|
|||
nmap -p 1080 <ip> --script socks-auth-info
|
||||
```
|
||||
|
||||
## Brute Force
|
||||
### Brute Force
|
||||
|
||||
#### Basic usage
|
||||
|
||||
### Basic usage
|
||||
```bash
|
||||
nmap --script socks-brute -p 1080 <ip>
|
||||
```
|
||||
### Advanced usage
|
||||
|
||||
#### Advanced usage
|
||||
|
||||
```bash
|
||||
nmap --script socks-brute --script-args userdb=users.txt,passdb=rockyou.txt,unpwdb.timelimit=30m -p 1080 <ip>
|
||||
```
|
||||
|
||||
### Output
|
||||
#### Output
|
||||
|
||||
```bash
|
||||
```text
|
||||
PORT STATE SERVICE
|
||||
1080/tcp open socks
|
||||
| socks-brute:
|
||||
|
@ -46,18 +49,22 @@ PORT STATE SERVICE
|
|||
### Basic proxychains usage
|
||||
|
||||
Setup proxy chains to use socks proxy
|
||||
```bash
|
||||
|
||||
```text
|
||||
nano /etc/proxychains4.conf
|
||||
```
|
||||
|
||||
Edit the bottom and add your proxy
|
||||
```bash
|
||||
|
||||
```text
|
||||
socks5 10.10.10.10 1080
|
||||
```
|
||||
|
||||
With auth
|
||||
```bash
|
||||
|
||||
```text
|
||||
socks5 10.10.10.10 1080 username password
|
||||
```
|
||||
|
||||
## More info: [Tunneling and Port Forwarding](../tunneling-and-port-forwarding.md)
|
||||
#### More info: [Tunneling and Port Forwarding](../tunneling-and-port-forwarding.md)
|
||||
|
||||
|
|