|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +## Franklin Agent 3.49.19 — the panel's task route can no longer read files outside the tasks folder |
| 4 | + |
| 5 | +Security fix. Follow-up to GHSA-jx74-262x-94p3, which 3.49.3 fixed for |
| 6 | +`/api/sessions/:id` only. Upgrade if you run `franklin panel`. |
| 7 | + |
| 8 | +- **Task ids cannot leave the tasks folder.** `/api/tasks/:runId` turned the |
| 9 | + id from the URL into a path without checking it, so |
| 10 | + `/api/tasks/..%2F..%2F<dir>` read `meta.json`, `events.jsonl` or `log.txt` |
| 11 | + from any folder on disk. Session ids and task run ids now pass one shared |
| 12 | + check that refuses `..`, `/`, `\` and null bytes. That covers session |
| 13 | + meta files too, which the cleanup code deletes. A bad task id now gets a |
| 14 | + 404. |
| 15 | +- **Every panel API route needs the page token, read-only ones included.** |
| 16 | + The checks for a local caller and a local Host header do not tell OS users |
| 17 | + apart, so another account on a shared machine, or anyone reaching the port |
| 18 | + through an `ssh -L` tunnel, could read session transcripts and the audit |
| 19 | + log. The panel page already sent its per-process token with every fetch. |
| 20 | + The live event stream now passes it as `?token=`, because EventSource |
| 21 | + cannot set headers. |
| 22 | + |
| 23 | +Thanks to Rajnish Tiwari, who reported the original issue. |
| 24 | + |
3 | 25 | ## Franklin Agent 3.49.18 — the Desktop beta.9 work lands in the agent |
4 | 26 |
|
5 | 27 | This release merges the Desktop 0.2.0 beta line back into the agent, so |
|
0 commit comments