logto-tunnel serves files outside --experience-path via path traversal

Summary

@logto/tunnel serves custom sign-in experience files from the --experience-path directory. When the tunnel service is reachable, a requester can use ../ path segments in a static asset request to read files outside that directory that the CLI process can read.

Details

The tunnel command accepts --experience-path as the local folder path for custom sign-in experience assets. packages/tunnel/src/commands/tunnel/index.ts enables createStaticFileProxy(path) when that option is set and sends non-Logto, non---experience-uri requests to that static proxy. The server is started with server.listen(port).

packages/tunnel/src/commands/tunnel/utils.ts builds the filesystem path as path.join(staticPath, fallBackToIndex ? index : request.url). For file asset paths, request.url is used directly. A request URL such as /../secret.txt resolves outside staticPath and is then opened with fs.open(requestPath, 'r'). There is no URL normalization and no containment check that the resolved path remains under the configured static directory before the file is read and returned.

The proof boundary is the packaged CLI end-to-end run. The filesystem read primitive was validated with equivalent Node HTTP handling for the affected code path, including that Node preserves /../secret.txt in request.url and that bare server.listen(port) binds to all interfaces on this platform.

PoC

1. Create a custom UI directory at /tmp/logto-ui/static with /tmp/logto-ui/static/index.html.
2. Create a sibling file outside the static root, for example /tmp/logto-ui/secret.txt.
3. Start the tunnel with logto-tunnel --endpoint https://<tenant-id>.logto.app --port 9000 --experience-path /tmp/logto-ui/static.
4. Request http://<host>:9000/../secret.txt.
5. The response body contains the contents of /tmp/logto-ui/secret.txt.