"AIT-GUI starts its web server on all network interfaces rather than honoring its configured host setting." — Cycode researcher Yuval Elbar
GHSA-p9r8-2q67-fp86: a 9.4 CVSS flaw in AIT-GUI through 2.5.1
On August 18 Cycode researcher Yuval Elbar disclosed a critical vulnerability in NASA's open-source AMMOS Instrument Toolkit (AIT)-GUI ground software. The flaw is tracked as GHSA-p9r8-2q67-fp86 and given a CVSS rating of 9.4. AIT-GUI is described in the project as the browser-based operator console for the AMMOS Instrument Toolkit, an open-source framework for ground data systems that communicate with instruments and spacecraft. Versions through 2.5.1 are affected; the project released a fixed version, AIT-GUI 2.5.2. No CVE had been assigned at the time of writing.
Unauthenticated API routes: /cmd, /script/run and /seq can issue commands
The vulnerability stems from multiple design and implementation failures in the AIT-GUI web stack. The API exposes state-changing endpoints without authentication, authorization or cross-site request forgery (CSRF) protection. The specific routes named in the disclosure — /cmd, /script/run and /seq — map directly to high-impact actions. According to the disclosure, /cmd can relay commands to the command bus, while /script/run and /seq can execute server-side scripts and command sequences.
Further compounding the risk, the /script/run and /seq endpoints construct filesystem paths from user-controlled input without adequate confinement, allowing files outside intended directories to be passed for execution. In short, unauthenticated requests to these routes can result in issuing spacecraft and instrument commands and running arbitrary server-side code.
The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadBrowser-based vector and host-binding failure enable indirect attacks
The disclosure highlights two operational details that widen the attack surface. First, AIT-GUI starts its web server on all network interfaces rather than honoring its configured host setting. Second, the state-changing routes accept browser-compatible form submissions without CSRF protection. As Cycode demonstrated, an operator who visits a malicious website can have cross-origin requests delivered to a local or firewalled AIT-GUI deployment without a CORS preflight, enabling the delivery of state-changing requests from the operator's browser.
That combination matters because these web functions sit between an operator console and command infrastructure. Security weaknesses in exposed operational technology (OT) environments can convert what would otherwise be basic access-control failures into routes to high-impact functions.
Fix released and project recommendations for mitigation
Cycode said the flaw has been fixed in AIT-GUI 2.5.2. The project recommends several concrete mitigations: implement authentication and authorization for state-changing endpoints; add CSRF protection; bind the server to its configured host; and add path confinement for the affected routes so filesystem paths cannot be constructed from untrusted input. Those changes address the disclosure's three core problems: exposed network binding, unauthenticated state-changing APIs, and unsafe filesystem handling.
What this means for ground operators, AIT-GUI maintainers, and NASA/JPL
- Ground operators and instrument teams: Operators who use AIT-GUI should treat local or firewalled deployments as potentially reachable via a browser-based attack if they or other users visit malicious pages. The disclosure specifically demonstrates that an operator accessing a host-local or firewalled deployment could be targeted through their browser.
- AIT-GUI maintainers and downstream integrators: The project-level recommendations — authentication/authorization, CSRF protections, host binding and path confinement — are the precise mitigations Cycode outlined and that are addressed in AIT-GUI 2.5.2.
- NASA/JPL and responsible parties: Infosecurity Magazine has contacted NASA/JPL for comment and said it will update the article with any response. At the time of the disclosure, no public agency comment was included in the report.
The flaw exposed a familiar but acute risk: web-facing operator consoles that accept state-changing requests without proper access controls can become direct conduits to critical infrastructure actions. The disclosure gives maintainers a short, specific checklist — and a released patch — but it also leaves a simple operational question: how many deployments were running vulnerable AIT-GUI instances, and which of those were exposed to operator browsers? Cycode has published the technical findings and a patch; affected teams now have the immediate task of inventorying instances and applying AIT-GUI 2.5.2 alongside the recommended mitigations.
