Repository navigation
Part II The Ground Segment
Ground segment attack and defense guide - covering uplink/downlink RF link architecture, TT&C (Telemetry, Tracking, and Commanding) attack vectors, mission control network security, ground station infrastructure vulnerabilities, and supply chain risks.
Covers: ground-space RF link architecture (uplink/downlink/crosslink), TT&C command injection and replay attacks, CCSDS frame structure and authentication weaknesses, ground station network lateral movement, mission control server hardening, and supply chain security for ground hardware.
Identify and assess vulnerabilities in the ground segment of a space system - the earth-based infrastructure that commands satellites and receives telemetry - without touching or transmitting to the satellite itself.
- Penetration testing a ground station or mission control network
- Assessing TT&C command authentication for a satellite operator
- Understanding how ground segment compromise enables satellite takeover
- Red-teaming space-adjacent infrastructure (ground networks, not orbital targets)
Every satellite system relies on a chain of RF links between ground and spacecraft:
Ground Station (Uplink)
โ
โผ
[Transponder / Receiver]
(Spacecraft)
โ
โผ
Ground Station (Downlink)
| Link | Direction | Purpose |
|---|---|---|
| Uplink | Ground โ Space | Commands, software uploads, data |
| Downlink | Space โ Ground | Telemetry, payload data, status |
| Crosslink / ISL | Space โ Space | Inter-satellite relay (proliferated LEO) |
| User Link | Space โ User terminal | End-user service delivery |
| Band | Frequency Range | Typical Use |
|---|---|---|
| L-band | 1โ2 GHz | Mobile SATCOM, GNSS |
| S-band | 2โ4 GHz | TT&C for many LEO spacecraft |
| C-band | 4โ8 GHz | Legacy FSS, broadcast |
| X-band | 8โ12 GHz | Military, government |
| Ku-band | 12โ18 GHz | Commercial FSS, VSAT |
| Ka-band | 26.5โ40 GHz | HTS, broadband (Viasat, Starlink) |
| V/W-band | 40โ75 GHz | Next-gen HTS |
- Unencrypted telemetry - Many legacy satellites downlink telemetry in cleartext CCSDS frames, allowing passive monitoring of spacecraft health, mode, and configuration
- Weak or absent command authentication - Early command systems used MAC codes that are now trivially breakable; some older birds have no authentication at all
- Signal intercept - Any sufficiently directional antenna aimed at the correct orbital slot can capture downlink signals; uplink intercept requires proximity to the ground station
- Replay attacks - Without command sequence counters, captured command frames can be replayed
The Consultative Committee for Space Data Systems defines the dominant protocol family:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ Mission-specific app โ (mission data, health reports)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ CCSDS CFDP / AOS โ (file transfer, advanced orbiting)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ Space Packet Protocol โ (packet framing, APID routing)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ TM / TC Transfer Frames โ (Telemetry / Telecommand frames)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ Sync & Channel Coding โ (ASM, LDPC, Reed-Solomon, turbo)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ RF / Physical โ (BPSK, QPSK, OQPSK, etc.)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Key CCSDS identifiers targeted during analysis:
| Field | Description | Security Relevance |
|---|---|---|
| APID | Application Process ID | Routes packets to subsystems; spoofing APIds targets specific spacecraft functions |
| VCID | Virtual Channel ID | Multiplexes data streams; may separate encrypted/unencrypted flows |
| Spacecraft ID (SCID) | Identifies the target spacecraft | Used to filter commands and telemetry |
| Sequence Counter | Monotonic packet counter | Anti-replay; absence is a vulnerability |
Modern mission control centers (MCCs) blend IT and operational technology (OT) in ways that introduce significant attack surface:
External Networks / Internet
โ
[Firewall/DMZ]
โ
Corporate IT Network
โ
[Air Gap / DMZ]
โ
Mission Control LAN
โโโโโโดโโโโโโ
โ โ
MOC/SOC Ground Station
(Ops) Network
Common MCC components:
- Mission Operations Center (MOC) - Operator consoles, display systems, command generation
- Flight Dynamics System (FDS) - Orbit determination, maneuver planning
- Telemetry Processing System - Ingests raw frames, decommutates engineering data
- Command Management System - Command authorization, sequencing, uplink management
- Data Archive - Historical telemetry, products, mission records
| Component | Common Technology | Common Issues |
|---|---|---|
| Operator workstations | Windows 10/11, Linux | Unpatched OS, legacy software dependencies |
| MCS applications | COSMOS, ITOS, GMAT, custom | Outdated frameworks, hardcoded credentials |
| Databases | Oracle, PostgreSQL, SQL Server | Weak authentication, excessive privileges |
| Network infrastructure | Cisco, Juniper | Default credentials, unpatched firmware |
| Remote access | VPN, RDP, TeamViewer | Weak MFA, exposed management interfaces |
- IT-side intrusion โ lateral movement to MCS network - Most historically successful path (mirrors IT/OT targeting in ICS attacks)
- Supply chain compromise - Malicious updates to MCS software or ground station hardware
- Remote access exploitation - VPN credential compromise, MFA bypass
- Insider threat - Privileged operators with unrestricted command access
- Removable media - USB-introduced malware in air-gapped or semi-air-gapped environments
The Sandworm/AcidRain attack against Viasat's KA-SAT network demonstrated how ground segment compromise translates directly to user-segment destruction:
- Attackers gained access to the management network via a misconfigured VPN concentrator
- Leveraged access to issue legitimate management commands to modems
- Deployed AcidRain wiper targeting VSAT modems via the provisioning system
- ~50,000 modems were bricked across Europe; Ukrainian military comms disrupted at war onset
Lessons: Management plane access to SATCOM infrastructure = mass end-device impact. Ground segment security directly protects the user segment.
Before any active testing, passive RF collection provides significant intelligence:
# Capture raw IQ data with HackRF (authorized lab/research use only)
hackrf_transfer -r capture.iq -f 437500000 -s 2000000 -g 40 -l 32
# Use SatDump for known satellite signals
satdump live noaa_hrpt baseband --source airspy --samplerate 6e6 --frequency 1707e6
# gr-satellites for CubeSat/amateur satellite decoding
python -m gr_satellites <satellite-name> --iq /path/to/capture.iqWith captured IQ data, work down the protocol stack:
-
Synchronization - Find the CCSDS Attached Synchronization Marker (ASM):
0x1ACFFC1D - Frame delineation - Transfer frame length is fixed per mission; determine from ASM spacing
- Header parsing - Extract SCID, VCID, frame counter, data field status
- Reed-Solomon / LDPC decode - Strip error correction coding
- Space Packet extraction - Parse APID, sequence flags, packet length
- Application data - Mission-specific; may require protocol documentation or reverse engineering
Wireshark supports CCSDS with appropriate dissectors. Custom dissectors can be written in Lua for mission-specific protocols.
โ ๏ธ Authorized testing only. Uplink injection toward an operational satellite is illegal without operator authorization.
| Attack Vector | Method | Prerequisite |
|---|---|---|
| MCS application exploitation | SQL injection, buffer overflow in command parser | MCS network access |
| Command file manipulation | Modify stored command sequences before uplink | File system access on MCS |
| Uplink interception + modification | MITM between MCS and modulator | Physical/logical access to RF chain |
| Replay of captured commands | Retransmit valid captured frames | Captured command traffic, weak sequence enforcement |
| Rogue ground station | Transmit on licensed frequency | Radio license, directional antenna, frequency/timing knowledge |
Ground systems that parse telemetry or expose northbound APIs are candidates for fuzzing:
# Conceptual fuzzer for CCSDS Space Packet parser
import boofuzz
import socket
def ccsds_space_packet(apid, data):
"""Build minimal CCSDS Space Packet"""
version = 0b000
type_bit = 0 # Telemetry
sec_hdr = 0
primary_header = ((version << 13) | (type_bit << 12) |
(sec_hdr << 11) | apid).to_bytes(2, 'big')
seq_flags = 0b11 # Standalone packet
seq_count = 0
seq_field = ((seq_flags << 14) | seq_count).to_bytes(2, 'big')
data_length = (len(data) - 1).to_bytes(2, 'big')
return primary_header + seq_field + data_length + data
# Fuzz the data field with boofuzz targeting a ground system parserOSINT sources for space ground infrastructure:
| Source | Information Available |
|---|---|
| FCC License Database (ULS) | US earth station licenses, frequencies, coordinates |
| ITU BR IFIC | International frequency notifications, earth station data |
| SatBeams / LyngSat | Transponder plans, EIRP maps |
| NORAD / Space-Track.org | TLE orbital elements for targeting geometry |
| LinkedIn / job postings | Technology stack inference (COSMOS, ITOS, specific SCADA) |
| Shodan / Censys | Internet-exposed ground system interfaces |
| Google Maps / satellite imagery | Physical ground station location confirmation |
External Recon
โโ> Identify IP ranges (NOC, ground station, corporate)
โโ> Shodan: product:"COSMOS" OR product:"Kratos" OR banner:"Mission Control"
โโ> Certificate transparency for domain enumeration
Initial Access
โโ> VPN/SSL VPN exploitation (CVEs, credential stuffing)
โโ> Exposed RDP / Citrix
โโ> Phishing targeting operations staff
Lateral Movement
โโ> IT network โ MCS DMZ โ MCS LAN
โโ> Credential harvesting (Mimikatz, secretsdump)
โโ> Service account abuse (privileged for automation)
Mission Impact
โโ> Command system access
โโ> Telemetry manipulation / suppression
โโ> FSW upload capability
โโ> Modem/terminal management access (user segment impact)
- Hardcoded credentials in legacy MCS deployments (often installed once and never rotated)
- Unencrypted internal protocols - some MCS components communicate via unencrypted UDP/TCP internally
- Weak authentication on web-based display systems and dashboards
- Outdated dependencies in Java-based or Python-based MCS stacks
- Insufficient input validation in command parameter interfaces
| Control | Implementation |
|---|---|
| Network segmentation | Strict IT/OT separation; MCS on isolated VLAN with unidirectional data diodes where possible |
| MFA everywhere | Require phishing-resistant MFA (FIDO2/hardware token) for all MCS access |
| Command authentication | Implement CCSDS Telecommand Authentication (TCA) or equivalent |
| Privileged access management | PAM solution for operator accounts; no shared credentials |
| Patch management | Separate patching cadence for MCS vs. IT; test in lab before ops deployment |
| Monitoring | Behavioral analytics on command issuance patterns; anomaly alerting |
| Supply chain | Firmware integrity verification; signed software updates |
๐ Use These Techniques Responsibly: Authorization is MANDATORY
Space systems are critical infrastructure - treat them accordingly.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
- README.md - SpaceSecurity section index
- PartI.md - Foundations: read before this Part
- PartIII.md - Space segment: the satellite side of the link
- ../SDR/sdr_hacking.md - SDR advanced: CCSDS protocol reversing and satellite RF signal capture
โญ Star this repo if you find it useful! โญ
๐ Source: SpaceSecurity/PartII.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Space Security
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics