An incorrect access control vulnerability in NASA cFS v7.0.1 allows remote, unauthenticated attackers to disrupt critical telemetry routing and compromise system data integrity.

The vulnerability exists within the TO_LAB application of the Core Flight System, where insufficient access controls permit unauthenticated actors to inject arbitrary commands. By sending specific TO_LAB add or remove subscription commands, an attacker can manipulate low-index subscriptions and introduce unauthorized data streams into the system.

Successful exploitation of this vulnerability poses a significant risk to the integrity and availability of telemetry data. By enabling unauthorized modification of data streams, an attacker could effectively blind mission operations or inject deceptive telemetry, potentially leading to operational failures or incorrect system state assessments. With a CVSS score of 7.5, this high-severity flaw requires immediate attention to prevent unauthorized command injection in mission-critical environments.

Immediate Action: As no official patch is currently available, administrators should restrict network access to the Software Bus and the TO_LAB application interface to trusted sources only. Monitor the vendor repository at https://github.com/nasa/cFS/issues/1076 for updates and the release of an official patch.

Proactive Monitoring: Implement strict logging and monitoring for all TO_LAB command traffic to identify anomalous subscription modifications or unexpected stream additions.

Compensating Controls: Deploy network-level access control lists (ACLs) to isolate the communication channels used by the cFS Software Bus, ensuring that only authorized ground support equipment can interact with the TO_LAB interface.

Public Exploit Available: No (there is no confirmed public exploit tooling available at this time).

Given the high CVSS score and the presence of a known proof-of-concept, this vulnerability represents a significant risk to mission-critical telemetry systems. Organizations utilizing NASA cFS v7.0.1 must prioritize network isolation and rigorous monitoring of command traffic while awaiting an official patch. Proactive hardening of the environment is essential to mitigate the risk of unauthorized stream manipulation.