1. The game that started with a wrong number

John Badham’s WarGames returns as the recalled work because its crisis begins with an attacker probing a boundary that the defenders assumed was too obscure to matter. Spacecraft command links were once treated the same way: hard to reach, expensive to exploit, and therefore safe. The reading shows that assumption is no longer defensible. Cheap software-defined radios, published protocols, and global COTS supply chains have moved the boundary much closer to the platform.

This entry reads about spacecraft cyber threats and attack vectors.

2. Where the risk concentrates

Shelby’s CubeSat risk assessment encodes 42 vulnerabilities using STRIDE and MITRE ATT&CK and finds that the highest-severity risks cluster in the communications and ground segments rather than onboard computing. Mean CVSS scores are 8.0–8.2 for communications and ground, versus 6.9 for onboard computing. The conclusion is practical: the interfaces most accessible to an adversary deserve the first increment of defensive investment.

The Aerospace Corporation’s threat-based report reaches a similar conclusion from a different angle. It warns that spacecraft have historically been designed as if the RF link or the ground system were the only boundary, with little internal protection if that boundary is breached. Defense-in-depth is the recommended correction.

3. The main attack vectors

The literature identifies a consistent set of vectors:

  • Uplink spoofing and command injection: an adversary within radio range transmits commands that the spacecraft accepts because the link lacks strong authentication. Legacy AX.25 and lightly secured CCSDS profiles are specifically called out as vulnerable.
  • Replay attacks: a previously recorded legitimate command is retransmitted to produce an effect the operator did not intend. Countermeasures include sequence numbers, timestamps, and nonce-based authentication.
  • Telemetry interception: unencrypted or weakly encrypted downlink exposes mission data, operational state, and possibly keys or firmware.
  • Jamming and denial of service: narrowband links and short passes are easy to disrupt, which can delay critical commands or prevent anomaly reporting.
  • Ground-system compromise: the mission control system, SDR firmware, or operator workstations are attacked, using the ground segment as a path to the spacecraft.
  • Supply-chain insertion: malicious or counterfeit components, firmware, or dependencies enter the flight or ground software before launch.
  • Lateral movement in constellations: once one node is compromised, weakly segmented inter-satellite links or shared credentials let the compromise spread.

4. Why small satellites are exposed

CubeSats and small satellites inherit the same threat model as large spacecraft but with tighter constraints:

  • Power budgets of 1–2 W leave little headroom for continuous cryptography or logging.
  • ARM Cortex-M class processors can run AES-256 and elliptic-curve cryptography, but sustained use competes with payload and housekeeping.
  • Short contact windows make continuous ground oversight impossible, so autonomous decisions must be pre-authorized and bounded.
  • COTS components and multi-vendor supply chains create inconsistent firmware provenance and patching practices.
  • Educational and start-up programs often assume benign users and prioritize function over security.

5. What this means for the desktop

The desktop is a small-satellite-class platform with autonomous maneuvering, power management, and payload operation. Its most exposed surfaces are likely to be:

  • the command uplink and telemetry downlink;
  • the ground station and mission control interfaces;
  • software update and firmware loading paths;
  • any inter-cell or inter-satellite links if the desktop grows into a constellation.

The reading suggests that a proportionate security strategy starts at those boundaries and works inward, rather than trying to harden every subsystem equally.

6. What this changes

  • Spacecraft cyber threats are not theoretical; they cluster in communications and ground segments.
  • Small satellites face the same threats as large spacecraft but with severe power and connectivity constraints.
  • The desktop’s security strategy should prioritize authenticated command links, encrypted telemetry, ground-segment hygiene, and supply-chain assurance.
  • The next entry will read about secure command authentication and link protection.