trails/apps/planner/app/routes/api.save-to-journal.ts
Ullrich Schäfer c3454641df
security: validate Planner callback URL to close an SSRF sink
The session callbackUrl becomes a server-side fetch target in
api.save-to-journal (POSTed with the callback bearer token, and the
journal's response is reflected to the caller). The /new query-param
loader already validated it, but the programmatic POST /api/sessions
entry point — anonymous, since the Planner is stateless — stored it
unvalidated. An attacker could make the Planner backend POST to
arbitrary hosts, including 169.254.169.254 and other internal targets.

- validateFetchUrl now blocks private / loopback / link-local /
  CGNAT / cloud-metadata hosts (IPv4, IPv6, IPv4-mapped) when an
  explicit allowlist isn't set. Gated on NODE_ENV=production && !E2E
  (the requireSecret idiom) so the dev/e2e journal-on-localhost save
  flow is unaffected. An explicit PLANNER_CALLBACK_ALLOWED_HOSTS still
  takes precedence and remains the full-closure control (it also stops
  DNS-name-to-private rebinding, which literal blocking does not).
- POST /api/sessions now validates callbackUrl exactly as /new does.
- api.save-to-journal re-validates immediately before the fetch
  (defense in depth: covers sessions persisted before this change and
  narrows the create→save rebinding window).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 22:18:18 +02:00

84 lines
3.2 KiB
TypeScript

// Server-side proxy for "Save to Journal". Looks up the session's
// callbackUrl + callbackToken (stored at /new time when the user came
// from the journal) and POSTs the GPX to the journal as a Bearer.
//
// Why this exists (planner-audit #2, Phase A): the previous flow had
// the browser fetch with the bearer token directly, exposing it in
// DevTools / to any XSS / browser extension. Now the token never
// leaves the planner's server-side trust boundary.
//
// Trust model: the same sessionId that grants Yjs membership grants
// save authority. Knowing the URL = ability to act. This matches the
// existing model — we're not strengthening or weakening it, just
// keeping the JWT off the wire to the browser.
import { data } from "react-router";
import type { Route } from "./+types/api.save-to-journal";
import { getSession } from "~/lib/sessions";
import { fetchWithTimeout } from "~/lib/http.server";
import { validateFetchUrl, getCallbackAllowedHosts } from "~/lib/url-validation.server";
interface SaveRequestBody {
sessionId?: unknown;
gpx?: unknown;
}
const MAX_GPX_BYTES = 5 * 1024 * 1024; // 5 MB — same ceiling as the Yjs doc cap
export async function action({ request }: Route.ActionArgs) {
if (request.method !== "POST") {
return data({ error: "Method not allowed" }, { status: 405 });
}
let body: SaveRequestBody;
try {
body = (await request.json()) as SaveRequestBody;
} catch {
return data({ error: "Invalid JSON" }, { status: 400 });
}
const sessionId = typeof body.sessionId === "string" ? body.sessionId : "";
const gpx = typeof body.gpx === "string" ? body.gpx : "";
if (!sessionId) return data({ error: "sessionId required" }, { status: 400 });
if (!gpx) return data({ error: "gpx required" }, { status: 400 });
if (gpx.length > MAX_GPX_BYTES) {
return data({ error: "gpx too large" }, { status: 413 });
}
const session = await getSession(sessionId);
if (!session) return data({ error: "session not found" }, { status: 404 });
if (!session.callbackUrl || !session.callbackToken) {
return data({ error: "session has no journal callback" }, { status: 400 });
}
// Defense in depth: re-validate immediately before the outbound fetch.
// Guards sessions persisted before callbackUrl validation existed, and
// narrows the window for a host that was public at create time but
// resolves private now.
const v = validateFetchUrl(session.callbackUrl, { allowedHosts: getCallbackAllowedHosts() });
if (!v.ok) {
return data({ error: "session callback URL is not allowed" }, { status: 400 });
}
let resp: Response;
try {
resp = await fetchWithTimeout(session.callbackUrl, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${session.callbackToken}`,
},
body: JSON.stringify({ gpx }),
});
} catch {
return data({ error: "journal unreachable" }, { status: 502 });
}
// Forward the journal's response (status + body) so the client UI
// can render the same error/success it would have before.
const text = await resp.text();
let payload: unknown;
try { payload = JSON.parse(text); } catch { payload = { raw: text }; }
return data(payload, { status: resp.status });
}