Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.
1. Restore the device to the manufacturer's 2.00.08 image.
- Connect the laptop to a wired LAN port of the device with an ethernet
cable.
- Open a browser (IE) to "http://<device_LAN_IP_address>"
(default <device_LAN_IP_address> is 192.168.1.1).
- Enter the username and password (leave the username field blank,
default password is admin) and click OK (if password
has not already been cached).
- Click "Administration" link on the upper right tab.
- Click the "Firmware Upgrade" tab.
- Click "Browse ...", select the
<HOME>/<PACKAGE>/wrt300n.bin
file on the cdrom.
- Click the "Update" button.
- Wait 3 minutes for the device to reboot.
IMPORTANT: the original web page to upgrade firmware does not work
on CB firmware. If you have tried to upgrade using the original
web page, and have gotten the error message "There is no new version of
firmware to upgrade", you will need to:
- See the CB User's Manual, section 12.7 "Firmware Upgrade Will ...".
2. IMPORTANT: when the device has come back up, manually power-cycle it again.
Testing has shown that an additional power-cycle after restoring the
original manufacturer's image results in better success of loading of the
wireless driver. This is also more similar to the operational scenario.
2a.IMPORTANT: wireless upgrade only works when wireless security is
disabled. Verify that wireless security is disabled, and if not,
disable it:
- Log on to the web page (as in step 1).
- Click the "Wireless" tab.
- Click the "Wireless security" tab.
- Set the "Security Mode" combo box to "disabled".
- Click the "Save Settings" button.
3. Disconnect the laptop's LAN cable, and wirelessly connect the laptop to the
device.
4. Verify connectivity of the wireless client and internet connectivity.
5. Next move on to the "OPERATIONAL PROCEDURES" section. When finished with
"OPERATIONAL PROCEDURES", return to step 6 in this section.
6. Verify a successful upgrade after the device has rebooted. After reboot,
reconnect your wireless client.
7. Login to CherryWeb (see CB User's Manual; requires a person logged into
a G terminal) and verify the device has beaconed. It should beacon at the
MM_INITIAL_BEACON_PERIOD_SEC parameter specified in
<HOME>/<PACKAGE>/flytrap.config.<SQSH_FILE>
plus 30 to 60 seconds for device boot/init time -- i.e., if
MM_INITIAL_BEACON_PERIOD_SEC has been specified as 60, then the device
should beacon after 90 - 120 seconds from the reboot event.
8. Firmware supports erasure of persistent data IF you upgrade from one
CB firmware to a different CB firmware. Note that, if a
device has CB firmware 'A' on it, then you upgrade to the manufacturer's