Vault7: CIA Hacking Tools Revealed
Navigation: » Latest version
Owner: User #14587667
JQJSTEPCHILD - Op2
IP Addresses
2911
gi0/0: 192.168.80.6/30 (TOR5 1/0/13)
gi0/1: XXX.XXX.XX.XXX (HFZ[CN])/28 (TOR5 1/0/3)
TRCore
VLANs used: 501,502, 503
Notes:
6/29/2015
- If I remove the 192.168.80.6 interface from the CoreSwx, then I can no long access the 2911.
- If I remove the XXX.XXX.XX.XXX (HFZ[CN]) interface from vlan501 on the CoreSwx, then I can still access the 2911. I placed a route on the CoreSwx (ip route XXX.XXX.XX.XXX (HFZ[CN]) 255.255.255.240 192.168.80.6).
7/2/2015
- Tested config (see "Test Log") below for steps performed.
8/20 - 8/21/2015
- Final testing of VPDN config.
- Folder containing operator instructions: \\10.9.8.21\share\Testing\JQJSTEPCHILD\Op2
Test Log
- Reload initial config
- configure replace flash:/2015-06-29_Base_Config
- reload
- show run
- Compare running-config with base config (using WinMerge).
- show history all
- show clock
- Copy Config
- Results in this message:
Jul 2 15:13:30.855: %IP_VFR-7-FEATURE_DISABLE_IN: VFR(in) is manually disabled through CLI; VFR support for features that have internally enabled, will be made available only when VFR is enabled manually on interface Virtual-Access1.1
- Results in this message:
Connect to VPNVirtual Private Network from Windows VMVirtual Machine (10.9.8.97)
- On Windows VM, confirm IP address of 10.10.10.X.
- On Windows VM, browse to http://172.20.11.104/whatismyip.php
- On Windows VM, disconnect from VPN.
- Clear up logs and reload router.
- After reload, log back into router and perform show run.
- Copy show run output and diff using WinMerge. Result should be identical to original config.