# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### Cherry Blossom

# TestProcedures

- 1
- 2
…
- 13
- 14
- 15
- 16
- 17
…
- 70
- 71

UNCLASSIFIED
Cherry Bomb Program Cherry Blossom Internal Test Procedures
Hardware Required:
• Wireless Router/Flytrap
• Client Computer
• Hub
• Server Computer with web server
• Ethernet cable(s)
Initial Setup:
• If the wireless router is currently a Flytrap, clear its NVRAM of
MissionManager (mm) specific data (i.e., telnet to the Flytrap and run
“killall mm && mm –x”). Perform a firmware upgrade on the Flytrap
using the image with the parameters specified above.
• The Beacon Tests do not require a wireless client connection, so it is
desirable (from a security aspect) to disable the Flytrap’s wireless interface
(i.e., through the device’s web configuration). Some Flytrap devices do not
support disabling of the wireless interface, so at the very least, enable WPA
(or WEP if that is all the device supports). If possible, remove the antenna(s)
from the Flytrap.
• Connect the client computer to the Flytrap (i.e., run an Ethernet cable from
the client computer to the Flytrap’s LAN). Verify connection via ping and
telnet.
4.1.1 Initial Beacon (IB) Period Test
Description: Tests Initial Beacon (IB) Period functionality.
Setup: see “Initial Setup” in section 4.1. Then, disconnect the Flytrap from the
internet (i.e., disconnect the cable from the Flytrap’s WAN port).
Run: telnet to the Flytrap and run “killall mm && mm –x && mm”. This will clear
MissionManager (mm) NVRAM and restart mm. mm logging should indicate how
long until the initial beacon event. As the IB Period in the test firmware is long (30
days), time can be shortened by advancing the ontime stored in Flytrap NVRAM
(i.e., typically via “killall mm && NVRAM set ots=xxx && mm”, where xxx is the
desired ontime in seconds). Note that using date to set clock forward or back
should have no effect (ontime should be immune to clock changes). The device
will attempt to send its IB once its ontime (the amount of time the device has
been powered on) reaches the IB Period, but the ontime is only updated
persistently every “INITIAL_BEACON_ONTIME_UPDATE_PERIOD_SEC” =
1800 seconds. Test that ontime is accumulating properly with respect to the IB
Period by power-cycling the device at intervals greater than 1800 seconds.
UNCLASSIFIED
15

- 1
- 2
…
- 13
- 14
- 15
- 16
- 17
…
- 70
- 71