[Security] Guest token rides in URL query string - leaks via access logs / history / Referer #21
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Identified during advisory review of #17 (guest checkout).
Problem
On the payment page the guest token (the customer's only credential) is passed as
?token=.... Query strings land in:Refererleakage (mitigated ifstrict-origin-when-cross-originpolicy holds, but that is implicit, not enforced in code)The magic-link landing
/gast-order/:tokenis inherently URL-based (accepted Notion/Stripe pattern), but the payment page does not have to expose the token in a query string.Severity
Warning
Suggested fix
sessionStorage/ a Pinia store / route state (or at minimum the URL fragment,#token=..., which is not logged) for the payment page.guest_tokenonce the order reaches a terminal state (sent/delivered/cancelled) so stale magic links stop working./gast-order/:tokenare rotated normally.References