Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a vulnerability in the Aerie/PlanDev sequencing-server, a system used for translating spacecraft activities into commands. The vulnerability allows unauthenticated attackers to insert arbitrary rules or write command dictionaries, potentially impacting how mission commands are generated. The main concern is confirming relevance and exposure due to the specialized nature of the affected technology.
- Unauthenticated attackers can alter command rules.
- Understanding its role in mission command generation.
- Confirm relevance and exposure of this specialized system.
Attack Path
How an attacker could exploit the issue
An unauthenticated attacker can exploit this vulnerability by sending a specially crafted request to the sequencing server. The server improperly handles session roles, allowing an attacker to bypass authentication checks by providing a forged session role in the request body. This allows the attacker to insert arbitrary expansion rules, which dictate how spacecraft activities are translated into commands, and to write to command dictionaries without any authentication.
- No authentication required.
- Send crafted request body to specific endpoints.
- Unauthorized control over command generation.
Live Threat
Current exploitation, exposure, and threat context
The Aerie/PlanDev sequencing-server could allow unauthenticated attackers to insert arbitrary expansion rules or write to command dictionaries. This is possible when the authorization middleware incorrectly prioritizes client-supplied session variables over JWT claims, or when specific endpoints are not protected by authentication. These actions could impact how spacecraft activities are translated into commands.
- Arbitrary rules and command dictionaries are at risk.
- Unauthenticated requests can exploit the system.
- Compromised command generation could occur.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Aerie/PlanDev sequencing-server is susceptible to critical vulnerabilities in its authorization middleware and command dictionary endpoints. Application owners and platform teams are likely responsible for addressing this issue. The immediate first step is to identify all instances of the affected technology, assess their reachability and criticality, and determine the accountable owner for remediation planning.
- Application and platform teams should own remediation.
- Verify system reachability and criticality first.
- Plan remediation based on risk exposure.
